Skip to content

chore: re-seal custom code for 1.101.0 spec (python/go/typescript/kotlin/ruby/php) The 1.101.0 spec regen failed at apply-patches: today's release cycle advanced each SDK repo's main ~3 commits past the 2026-05-30 seal, so the new generation conflicted with the stale sealed baseline. Re-sealed against current main using the fork stlc (build -> resolve embedded-spec/version/description drift by taking generated HEAD -> --continue). java unchanged (its seal still applies in CI). See LEARNINGS §6 (re-seal) + the seal-follows-main invariant (to be added). #1260

chore: re-seal custom code for 1.101.0 spec (python/go/typescript/kotlin/ruby/php) The 1.101.0 spec regen failed at apply-patches: today's release cycle advanced each SDK repo's main ~3 commits past the 2026-05-30 seal, so the new generation conflicted with the stale sealed baseline. Re-sealed against current main using the fork stlc (build -> resolve embedded-spec/version/description drift by taking generated HEAD -> --continue). java unchanged (its seal still applies in CI). See LEARNINGS §6 (re-seal) + the seal-follows-main invariant (to be added).

chore: re-seal custom code for 1.101.0 spec (python/go/typescript/kotlin/ruby/php) The 1.101.0 spec regen failed at apply-patches: today's release cycle advanced each SDK repo's main ~3 commits past the 2026-05-30 seal, so the new generation conflicted with the stale sealed baseline. Re-sealed against current main using the fork stlc (build -> resolve embedded-spec/version/description drift by taking generated HEAD -> --continue). java unchanged (its seal still applies in CI). See LEARNINGS §6 (re-seal) + the seal-follows-main invariant (to be added). #1260

Triggered via pull request June 1, 2026 08:52
Status Skipped
Total duration 1s
Artifacts

ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in