ci: add Changesets release workflow#10
Merged
Merged
Conversation
Automate versioning + publishing the same way Rudder does: on push to main, changesets/action opens (or updates) a 'chore: version packages' PR while changesets are pending, and runs `pnpm release` (build packages/* + `changeset publish`) once that PR merges and no changesets remain. Removes the manual `changeset version` + passkey publish loop. Requires an NPM_TOKEN repo/org secret (automation token, publish scope); RELEASE_PAT is optional and falls back to GITHUB_TOKEN.
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
Adds
.github/workflows/release.ymlso GemStack releases the same way Rudder does. On push tomain,changesets/action:chore: version packagesPR while changesets are pending (runspnpm changeset:version), andpnpm release(turbo build --filter=./packages/*+changeset publish) once that PR merges and no changesets remain.This removes the manual
pnpm changeset version+ passkeynpm publishloop used for@gemstack/ai-sdk@0.1.0and0.2.0.Required before it can publish
NPM_TOKENrepo (or org) secret — an npm automation token with publish rights on the@gemstackscope (automation tokens bypass the passkey/OTP prompt, which is what blocked CI publishing before).RELEASE_PAT— a PAT/App token so the bot's pushes tochangeset-release/maintrigger CI on the version PR. Falls back toGITHUB_TOKENif unset (releases still work; the version PR just may need a nudge to get checks).Until
NPM_TOKENis set the workflow runs but the publish step no-ops/fails at auth, so add the secret before relying on it.Notes
rudderjs/rudder'srelease.ymlintent, in GemStack's lighter@v4-pinned style (matches the existingci.yml).