feat(maintenance/v1): automate releases with Changesets#58
Closed
toiroakr wants to merge 1 commit into
Closed
Conversation
Mirror main's Changesets-based release automation on maintenance/v1: a PR that adds a .changeset/*.md file gets picked up by release.yaml, which opens/updates a Version Packages PR bumping package.json and CHANGELOG.md. Once that merges, the same workflow tags the new version and creates a GitHub release targeting maintenance/v1 explicitly, which update-major-tag.yaml then picks up as usual. - .changeset/config.json + README.md: same scaffold as main, but baseBranch: maintenance/v1. - package.json: add name/version (1.7.0, matching the current v1.7.0 release) tracked independently from main's, @changesets/cli devDependency, and a changeset script. - .github/workflows/release.yaml: triggers on push to maintenance/v1 instead of main; the release step passes --target maintenance/v1 explicitly since gh release create otherwise targets the repo's default branch (main). - CLAUDE.md: document the automated flow, replacing the manual gh release create --target steps.
Contributor
Author
|
Closing — pushing this directly to maintenance/v1 instead (no branch protection on it yet). |
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
Mirror #57's Changesets-based release automation on
maintenance/v1:.changeset/*.mdfile to a PR (viapnpm changeset) describes the changeand its bump type.
release.yaml(usingchangesets/action, nopublish-script) opens/updates a"Version Packages" PR from accumulated changesets, bumping
package.jsonandCHANGELOG.md.release from the changelog entry, explicitly targeting
maintenance/v1(
gh release create --target maintenance/v1) since that's not this repo's defaultbranch. Idempotent against unrelated later pushes (checks
gh release viewfirst).update-major-tag.yamlpicks up the new release exactly as before.CLAUDE.mdis updated to describe this flow, replacing the manualgh release create --targetsteps.package.json'sname/versionhere are independent frommain's — separate lines,versioned separately (starts at
1.7.0, the current latestv1release).