Pin order 2.10.2 and checkout 0.13.2 - #1196
Merged
Merged
Conversation
Both releases move to Temporal Go SDK 1.49.0 and passed the full local-stack release audit (A/B/C + C22) on their merged SHAs. The worker pins start a Progressive rollout through the Worker Controller, which is the rollout drill for #1194.
This was referenced Oct 2, 2026
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
1 participant
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.
What
The Kind pins for the G4 release: Temporal Go SDK 1.49.0, from #1107.
order(services/order.yaml)order-workerWorkerDeploymentcheckout(services/checkout.yaml)checkout-workerWorkerDeploymentRelease gate
The full local-stack E2E release audit ran from scratch on order
d1dafd5and checkout8afc665:The first run failed C22: Weaver found the SDK's new
failure_reasonattribute ontemporal_activity_execution_failed(153 violations). duynhlab/pkg#117 declared it in the registry, and the stack was recreated and the whole audit rerun, which passed.C9 was settled by durable evidence, as the runbook allows: 5 fulfillments
Completed= 5 audit orders terminal. The per-process counter reset after the A14/A15 restarts.The tags carry GitHub Releases, and both images are signed and Trivy-clean.
Verified on Kind (branch overlay, with #1194's controller 1.12 overlaid)
Progressive rollout on controller 1.12, from the controller log:
DrainingDrainingStatus and gates:
ConnectionHealthy,ReadyandRolloutComplete.make e2e GATE=kind: K4.1–K4.8, K5.2–K5.9 and SG.1–SG.4 all PASS. SG.4 shows Pinned on the new Current build.Alerts after the rollout, all accounted for:
KedaScaledObjectErrors, briefly: the new version's ScaledObject queriedDescribeWorkerDeploymentVersionat 07:56:42Z, seconds before the version registered. There were no errors after that, and the alert cleared.EdgeUpstreamUnhealthy: pending during the pod swap, then cleared.TemporalServiceErrorRateHigh, pending at 4.6% (threshold 5%): this is pre-existing. The rule countsNotFound, mostlyQueryWorkflowNotFound, which was already at 0.26–0.53/s 3–6 h before this change. A follow-up should excludeNotFound, as the persistence rule already does.*HighOverallErrorRate/CheckoutAvailabilityUnknownSKU: produced by the k6 staff/operator suites' deliberate error rows. Yesterday's release recorded the same.After merge:
make flux-pushfrom main. #1194 merges with or before this one, so the controller stays on 1.12.