Repository navigation
fix(changesets): stop ignoring private app packages - #4122
Merged
Merged
Conversation
@quri/hub, @quri/squiggle-ai and @quri/content are private (never published), but were in the changesets `ignore` list. Changesets for them were never consumed, so they piled up and forced the release workflow onto the "version" path forever — it could never reach "publish" (the empty "No commits between main and changeset-release/main" error). Removing them from `ignore` lets their changesets be consumed into their own changelogs and version bumps; being private, they still never publish to npm. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
The release workflow could never reach the publish step: changesets for the private app packages (hub, AI, content) were never consumed, so they piled up and kept the workflow on the version path (the "No commits between main and changeset-release/main" error).
These packages are private and never publish to npm, so ignoring them was redundant. Removing them from the ignore list lets their notes become changelogs and unblocks publishing.
🤖 Generated with Claude Code