chore(ci): trigger codegen verification post v0.12 release#31
Merged
Conversation
Trivial doc-comment touch to trigger a fresh CI run now that:
- The v0.12.0 release is published to the public registry
(npm / PyPI / Go proxy / crates.io).
- The codegen-v1beta0 tag was force-moved to the v0.12.0 HEAD so
the rendered templates target the published SDK.
Together this should clear the codegen job, which was structurally
red before the release tags landed.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The script still looked for `async transfer(` (the pre-port template emitted async resolve methods on Client) and `PROFILES` (the pre-port template emitted a single aggregate). After the unified-builder port, the rendered Client method is sync and returns a TxBuilder, and profiles are emitted as individual `_LOCAL_PROFILE` / `_PREPROD_PROFILE` named items plus a typed `Profile` string-union — per sdks/sdk-spec/codegen/generated-surface.md. Replaces the stale greps and adds checks for the new shape (Profile type union, per-profile consts, Tx3ClientBuilder.fromParts seeding, withPartyUnchecked routing). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
My previous grep looked for `_LOCAL_PROFILE` / `_PREPROD_PROFILE` (the shape used in the Python and Go templates, which prefix with an underscore to flag the const as module-private). The TS template emits `LOCAL_PROFILE` / `PREPROD_PROFILE` without the prefix — TS uses `#private` for true privacy and the convention in this codebase is no leading underscore for module-scope constants. Drops the leading underscore from both greps to match what the template actually renders. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Summary
Trivial doc-comment edit to
codegen-check.sh— exists to trigger a fresh CI run now that the fleet v0.12.0 release is published and thecodegen-v1beta0tag has been force-moved to point at the v0.12.0 HEAD.The codegen job was failing on every prior CI run because it pulls the runtime SDK from the public registry, and the template was rendering against a v0.11-pinned SDK that did not yet expose
Tx3ClientBuilder.fromParts. After the v0.12.0 publish + thecodegen-v1beta0tag move, both halves now agree.Decision after CI
codegenpasses ✅ → close the PR (the doc comment is cosmetic; not worth merging on its own).codegenfails ❌ → fix the underlying issue in this branch and merge.🤖 Generated with Claude Code