Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

npm publishing with wrong version tag #127

Open
lacolaco opened this issue Sep 8, 2022 · 4 comments
Open

npm publishing with wrong version tag #127

lacolaco opened this issue Sep 8, 2022 · 4 comments

Comments

@lacolaco
Copy link

lacolaco commented Sep 8, 2022

image

Git tag is correctly created, but npm publishing is failed due to the wrong version.

msr: v3.0.0
@lacolaco
Copy link
Author

lacolaco commented Sep 8, 2022

It works properly with msr v2.13.0. This behavior is happening after bumping msr to v3.

@antongolub
Copy link
Collaborator

This may be a side effect of the bumped semrel version: v2.13.0...v3.0.0. Could you check this hypothesis (yarn + resolutions)? Maybe we should move semrel to peer deps and define '>= 17 'range.

@Badisi
Copy link
Contributor

Badisi commented Oct 25, 2022 •
edited
Loading

Similar issue was opened on @semantic-release/npm: #504 and you can read my comment for further explanation.

This is basically due to an npm issue with workspaces but could be easily fixed in @semantic-release/npm.

@donaldxdonald
Copy link

any progress? 👀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@Badisi @lacolaco @antongolub @donaldxdonald