fix: replace @semantic-release/npm with @anolilab/semantic-release-pn… #199
Conversation
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
…pm to properly resolve workspace references
|
🎉 This PR is included in version mycoder-agent-v1.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version mycoder-v1.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Fix incorrect publishing of workspace references in package.jsons
This PR resolves issue #198 by implementing the
@anolilab/semantic-release-pnpmplugin to properly handle pnpm workspace references during the release process.Problem
When using the standard semantic-release npm plugin, workspace references in package.json (like
"mycoder-agent": "workspace:*") were being published as-is instead of being resolved to proper version numbers. This happens because semantic-release by default uses npm to do the publishing, which doesn't properly handle pnpm workspace references.Solution
@anolilab/semantic-release-pnpmas a dev dependency to the root package.json.releaserc.jsonfiles in both packages (agent and cli) to use@anolilab/semantic-release-pnpminstead of@semantic-release/npmReferences
Closes #198