fix(changeset): enable versioning and tagging for private package - #18
Merged
Conversation
Add `privatePackages` config to `.changeset/config.json` so that `changeset tag` creates git tags for the private package, which enables the release workflow to produce GitHub Releases. Co-Authored-By: Claude Opus 4.6 <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.
Type of Changes
Description
Changeset release workflow was not triggering GitHub Releases because
package.jsonhas"private": trueand.changeset/config.jsonwas missingprivatePackagesconfiguration.By default, Changesets skips version bumps and tag creation for private packages. This meant:
changesets/actionrunspnpm changeset tagchangeset tagsees the package is private → skips tag creationpublishedoutput isfalseAdding
privatePackages: { version: true, tag: true }fixes the entire flow:changeset PR merged → git tag created → GitHub Release generated → extension zip uploaded.
How Has This Been Tested?
Verified the config change is valid JSON and matches the changesets config schema. Full verification will happen when merging the next release PR.
Checklist
Additional Information
Reference: read-frog uses the same
privatePackagesconfig for their private browser extension package.🤖 Generated with Claude Code