You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thank you so much for creating this package, we use it for all of our projects.
I've bumped into an issue with one of our repositories now though. With every draft I create using npx release patch, every commit on master is shown as to be included in the draft. Here are some things I've tried:
making sure the remote tags match the local tags
specifying the previous tag using the -t option
releasing a draft containing all commits to check whether the second time I try it the problem will be solved. It wasn't.
Not really sure what to try next. Could you help me out?
The text was updated successfully, but these errors were encountered:
Solved! The very first tag we created in this repository was 1.0.0-canary.0. After that we switched back to 0.0.x, that was the problem. Every new tag wasn't the tag with the highest version number, that caused the trouble.
Removed the first tag and everything worked perfectly!
First of all, thank you so much for creating this package, we use it for all of our projects.
I've bumped into an issue with one of our repositories now though. With every draft I create using
npx release patch
, every commit on master is shown as to be included in the draft. Here are some things I've tried:-t
optionNot really sure what to try next. Could you help me out?
The text was updated successfully, but these errors were encountered: