This message was deleted.

we’re working on support for this. depending on your use case you may be able to workaround today by either untracking it or set it as your trunk. what are the details — do you stack off of it?

thats a good q re stacking on top of it - trying to think of the best approach. but yeah untracking now works. if you are following the changesets workflow, as of now the way i think of it is in terms of prereleases:

main (version is 0.0.1)
A
B
C -> prerelease with a version that's a tag, i.e. version 0.0.2-prerelease.0 (this branch should be fixed to track what exactly was released)
D
E -> prerelease b  with version 0.0.2-prerelease.1 (should be fixed)

if there is any feedback in any of the stacked branch PRs, you can do fixed in those branches, but you don't want to rebase them into the pre-release branches as those should be tracking what was released in them. when ready to release, merge all branches (except prerelease) to

main

then:

main
release (with bumping version from 0.0.1 to 0.0.2)

merge release branch to

main

I think this is a perfect use case for a command called

gt pin

oh! i didn't know about

gt pin

thats great

upcoming yes, sorry that that wasn't clear above!

great!