chore: automate releases with changesets#17
Open
TimPietruskyRunPod wants to merge 1 commit intomainfrom
Open
Conversation
- Add @changesets/cli and @changesets/changelog-github for automated version bumping, changelog generation, and GitHub Release creation - Add changesets.yml workflow: creates "Version Packages" PR on merge, then creates GitHub Release when that PR is merged - Simplify release.yml: remove tag push trigger and manual release creation step (changesets handles this now) - Finalize CHANGELOG.md at 1.3.0 - Rewrite CONTRIBUTING.md with new release workflow docs - Add .gitignore for node_modules
de9a9c0 to
5107e4d
Compare
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
@changesets/clito automate version bumping, changelog generation, and GitHub Release creationchangesets.ymlworkflow: on merge tomain, creates/updates a "Version Packages" PR; when that PR is merged, creates a GitHub Release which triggers the existingrelease.ymlto build Docker imagesrelease.ymlby removing the tag push trigger and manual release creation step (changesets handles both now)CHANGELOG.mdat version1.3.0as the baseline for changesetsCONTRIBUTING.mdwith the new automated release workflow docsHow it works
npx changesetin their PR branch and commit the.changeset/*.mdfilemain→ changesets action creates/updates a "chore: version packages" PR (bumpspackage.json, updatesCHANGELOG.md)release.yml→ builds and pushes Docker imagesTest plan
changesets.ymlruns, finds no pending changesets, checks for release1.3.0— should be a no-op (or create1.3.0release if it doesn't exist)npx changeset(pickpatch, write a description) → merge itrelease.ymltriggers