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
{{ message }}
Repository navigation
Handling patch-releases made on main while a feature is still in progress (or minor releases while a breaking change is in progress)
#1924
When working on a branch, I sometimes make a prerelease. If I am working on a branch that does a feature bump (or breaking change), and I merge from the trunk branch after there has been a patch release there, then Knope doesn't take into account my prior prerelease tags, because it sees that there is a more recent release that is not an ancestor of the prior prereleases. If instead I rebase onto the trunk, I lose the tags unless I manually move them1; but in general moving tags isn't really a good practice anyway.
One fairly simple workaround I've thought of is to just manually create a new empty commit and tag it with the next prerelease version, so that the next prerelease after that starts with the correct number.
Any other suggestions for how to deal with this? #991 would be helpful here as well.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
When working on a branch, I sometimes make a prerelease. If I am working on a branch that does a feature bump (or breaking change), and I merge from the trunk branch after there has been a patch release there, then Knope doesn't take into account my prior prerelease tags, because it sees that there is a more recent release that is not an ancestor of the prior prereleases. If instead I rebase onto the trunk, I lose the tags unless I manually move them1; but in general moving tags isn't really a good practice anyway.
One fairly simple workaround I've thought of is to just manually create a new empty commit and tag it with the next prerelease version, so that the next prerelease after that starts with the correct number.
Any other suggestions for how to deal with this? #991 would be helpful here as well.
Footnotes
I've asked about having a simpler way to rebase and move the tags to deal with this case: https://github.com/jj-vcs/jj/discussions/9587 ↩
All reactions