Repository navigation
Mark Cloud Run Serverless Workers as Public Preview - #5383
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
📖 Docs PR preview links
|
flippedcoder
approved these changes
Oct 1, 2026
blake
approved these changes
Oct 1, 2026
lennessyy
enabled auto-merge (squash)
October 1, 2026 21:21
Duncanma
pushed a commit
that referenced
this pull request
Oct 2, 2026
Co-authored-by: Lenny (Temporal) <lennessyy@users.noreply.github.com>
Duncanma
added a commit
that referenced
this pull request
Oct 5, 2026
* Derive ReleaseNoteHeader featureName tests from the feature map Two ReleaseNoteHeader tests hard-coded a feature's release stage (serverlessWorkersCloudRun as Pre-release, cloudCli as Public Preview), so they broke whenever a feature changed stage. #5383 moved serverlessWorkersCloudRun to Public Preview and the override test started failing. Both tests now pick a feature from FEATURE_RELEASE_TYPES and read the expected label from RELEASE_NOTE_LABELS, which mdx-to-md.mjs now exports. The override test sets an explicit type that always differs from the mapped one. The self-closing test prefers a feature whose stage differs from the publicPreview default, so a broken lookup can't pass by falling through to the default. * Derive paired-form ReleaseNoteHeader test from the feature map The paired-form featureName test used standaloneActivity, which #5290 removed from FEATURE_RELEASE_TYPES at GA. Since then the test has only exercised the publicPreview default, not the featureName lookup. It now shares a pickMappedFeature() helper with the self-closing test, which prefers a feature whose stage differs from the default.
Duncanma
added a commit
that referenced
this pull request
Oct 6, 2026
* Combine SLA and Service availability into /cloud/slo Merge the Evaluate SLA and Service availability pages into a single "Uptime, latency, and SLOs" page in the Temporal Cloud section, next to RTO/RPO. The page opens with the operational-practices disclaimer and a summary of every published SLA and SLO number, then has Uptime and the SLA, Latency, Visibility API availability, and Throughput sections. The old section anchors are kept so redirected deep links still land. - Redirect /evaluate/cloud/sla and /evaluate/cloud/service-availability to the new page, and point older redirects straight at it. - Keep an Evaluate > Temporal Cloud sidebar link to the page. - Update inbound links across docs/. - Point CODEOWNERS at the new page and fix stale evaluate/ paths. * Update docs/cloud/slo.mdx Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * removing cross link from evaluate * Clarify Schedule overlap and buffering behavior (#5288) * Document Schedule overlap and buffering pitfalls * Move Schedule common pitfalls to troubleshooting * Mark Cloud Run Serverless Workers as Public Preview (#5383) Co-authored-by: Lenny (Temporal) <lennessyy@users.noreply.github.com> * Fix invalid redirects and add a redirect rule validator (#5384) * Fix invalid redirects in vercel.json and remove the getting-started page. * Add a redirect rule validator and run it in the Check Redirects workflow. * Link to temporal.io/sla instead of restating the SLA The legal SLA at temporal.io/sla is the source of truth, and the docs had drifted from it: they claimed the SLA covers Worker commands, polling, and Nexus (it covers StartWorkflowExecution, SignalWorkflowExecution, and SignalWithStartWorkflowExecution) and that rates reset quarterly (they are per monthly billing cycle). - /cloud/slo: replace the SLA section, error-rate formula, and excluded errors list with an Uptime section that states the 99.99% objective and links to the SLA. - Remove SLA percentages from High Availability, Evaluate overview, glossary, and best-practices prose; link to temporal.io/sla instead. - Stop claiming SLA coverage for Nexus and Standalone Activities; keep the latency SLO statements. - Point SLA links in rto-rpo, service-health, operation-api, and visibility at temporal.io/sla. - Redirect /evaluate/cloud/sla and /cloud/sla to /cloud/slo#uptime. - Add an SLA card to the Evaluate overview. * Address review feedback on /cloud/slo - List the contractual SLA row first in the summary table. - Qualify the RTO/RPO rows by replication type, linking to the summary on the RTO/RPO page. - Collapse the January 2026 and March 2024 latency tables into an "Earlier measurements" details block. - Drop the Visibility question that repeated the section heading. - High Availability: drop "including cloud provider outages", which the legal SLA doesn't state. - Cloud Ops API: stop listing Workflow and Activity execution as SLA coverage; point to the SLA for covered APIs. - Service health: describe automatic failover behavior instead of attributing it to the SLA. - Standalone Activities: name the latency and Visibility SLOs that apply instead of claiming every SLO matches. --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Harani Mukkala <harani.mukkala@temporal.io> Co-authored-by: Lenny Chen <55669665+lennessyy@users.noreply.github.com> Co-authored-by: Lenny (Temporal) <lennessyy@users.noreply.github.com>
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cloud Run Serverless Workers are entering Public Preview. Update the release-stage mapping and banners across the Cloud Run guides and related index pages, and remove the Pre-release access and future-preview wording.
Cloud Run banners now say: “APIs and configuration may change before the stable release.” AWS Lambda and Amazon Bedrock AgentCore Runtime retain their existing release stages.
This PR contains no sample, Worker identity, OpenTelemetry, or Snipsync changes and has no dependency on the upstream sample PRs. Those changes remain in #5292.
Validation: production build and CI-scoped Vale passed. A scope check verified that all changes are limited to release banners, the Cloud Run release-stage reference, and the Cloud Run feature mapping; sample code is unchanged.