fix: changeset package name is "kit", not the Go module path#70
Merged
Conversation
The changesets workspace is the package.json package ("kit"); naming the
Go module path made `changeset version` fail on main ("Found changeset
credits-economy-abi for package github.com/shellcade/kit/v2 which is not
in the workspace"), blocking the Release workflow.
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.
The Release workflow on main is failing at
changeset version:The changesets workspace package is
kit(package.json), not the Go module path — #69's changeset used the wrong name. One-line frontmatter fix, matchingquiet-timers.md.🤖 Generated with Claude Code