Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Fixing previously unconventional version
See original GitHub issueI tried to migrate my repo to using semantic-release-monorepo from just autopublish. However since previously the packages were commited manually, I need to fix the tags to match the HEAD commit. However not really sure what tag name should i push to fix each package?
Would be grateful if given an example!
Issue Analytics
- State:
- Created 6 years ago
- Comments:32 (16 by maintainers)
Top Results From Across the Web
How to version bug fix of library for earlier release?
What your version 2.0.2 requires is again subject of a risk analysis. Assumed libs 1.5.0 and 1.5.1 both contain still a bug which...
Read more >Google-specific AMP Issues - Search Console Help
To fix, use a larger image according to our guidelines. AMP page domain mismatch, The AMP page is hosted on a different domain...
Read more >Homebrew install specific version of formula? - Stack Overflow
Feel free to add a note if you found the old version better.) Let's start with the simplest case: 1) Check, whether the...
Read more >Fixing Ungrounded Outlets - An Alternative Option to Rewiring ...
Older homes usually have two-prong outlets instead of today's standard three-prong outlets that include a ground wire.
Read more >Versions Maven Plugin – Version Rules - MojoHaus
The versions-maven-plugin knows three rules for comparing version numbers: maven, The standard Maven 2.x and 3.x version numbering scheme.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It looks like
@semantic-release/npmversion2.6.1that was released the other day may be the culprit. Due to an internal change,semantic-release-monorepois unable to wrap it (issue).Unfortunately, both
semantic-releaseversions 11 and 12 have a minor version (^2.0.0) dependency on@semantic-release/npm. For now, you should be able to work around it by manually installing an earlier version of@semantic-release/npm, but its obviously less than an ideal workaround going forward. Hopefully the maintainers ofsemantic-releaseare open to finding a solution.Try version
4.1.0. It will log the version being used for each plugin (when passing--debug). It should help shed some more light on what’s going on.You should see a line like this: