feat(sdk): automate reviewed npm release tags - #1425
Open
samuv wants to merge 1 commit into
Open
Conversation
Signed-off-by: Samuele Verzi <samu@stacklok.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
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
Automate TypeScript SDK release preparation and tagging with the existing release GitHub App. A maintainer dispatches a version-bump workflow, reviews and merges the generated two-file PR, then approves the npm staging environment and the staged npm candidate.
Development stage
Contract linkage
v0.1.0tag.Changes
Create TypeScript SDK Release PR, manually dispatched frommainwith a patch/minor/major choice.sdk/typescript/VERSIONas an SDK-only release trigger, kept equal topackage.json.sdk/typescript/vX.Y.Z.npm-publisheven when prevent-self-review is enabled.package.json, preventing stale hard-coded runtime versions after a bump.Security boundaries
mainand use the existingreleaseEnvironment.GITHUB_TOKENnever pushes the release branch or tag; App-authored events cascade into PR CI and the npm tag workflow.package.jsondependency edits cannot trigger tagging; onlysdk/typescript/VERSIONdoes.Test plan
task lint:actionstask sdk:lint sdk:typechecktask docsThis PR does not create or publish a new SDK version. After merge, the next release begins by dispatching
Create TypeScript SDK Release PRfrommain.