chore(release): version packages - #114
Merged
Merged
Conversation
✅ Deploy Preview for contentrain-ai ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
contentrain@0.9.1
Patch Changes
@contentrain/mcp@3.0.1
Patch Changes
@contentrain/query@7.0.3
Patch Changes
@contentrain/types@1.0.1
Patch Changes
0430ce2: Republish as 1.0.1 — 1.0.0 is permanently unavailable on npm
@contentrain/types@1.0.0was published on 2025-01-04 and later unpublished.npm reserves an unpublished version number forever, so when the release
sequence reached 1.0.0 again the registry refused it:
Five of the six packages in that release published successfully; only types
failed. But
workspace:*resolves to an exact version at publish time, so@contentrain/mcp@3.0.0,@contentrain/query@7.0.2andcontentrain@0.9.0all went out pinned to
@contentrain/types@1.0.0— a version that does notexist and cannot be created. Installing any of them fails with ETARGET.
This bumps types to 1.0.1 and carries the three dependents with it. Nothing
about the code changes; 1.0.0 never reached anyone.
Worth noting for later: had the workspace used
workspace:^rather thanworkspace:*, the published range would have been^1.0.0and this wouldhave healed itself the moment 1.0.1 landed, without needing to republish the
dependents.