I realise i'm one of the few who choose to use the beta version of the graphite CLI but as an fyi, when I updated from v1.7.20 to v1.8.1, all but 1 of my branches became untracked by graphite. sorry i don't really have any more reproduction-y things, and it could just be a one off, but just wanted to report it in case?

(If applicable) To help us repro, please send the following if you haven't already: - PR links, screenshots, and/or debug output if applicable - Repro steps - Does this happen consistently? Just to you or others on your team also? - Is this a regression? Is the problem new? - If you're having an issue with the CLI, please send us debug logs using

gt feedback --with-debug-context <any message>

i submitted with debug context and linked to this thread ^

hey Ally, after upgrading did you run a

gt

command that seemed to hang? This would have needed to complete to migrate your existing branches to be compatible with 1.8

hmmm i don't remember to be honest, sorry about that 😕 not really expecting (or needing) anything to be done, was just hoping extra eyes from a beta tester would maybe be helpful!

gotcha, yeah we're going to put out guidance about what'll happen under the hood during the upgrade once the Beta is made public in the changelog this week. You're ahead of the curve 😅

😄 all good! out of curiousity, is there anywhere i can see a changelog for beta versions of the clI? as far as i could see, it's maybe moving to be more native or something?

If you run

gt --version

what output do you get? Possibly you got reverted back to the pre-

1.8

stable version

i'm still on 1.8.1. i was just curious if there was a version of this with beta versions too but all good if not! https://graphite.com/docs/cli-changelog

We think what might have happened is you got auto-upgraded to

1.8.0

which can cause branches to untrack. We deprecated that version shortly afterward, and

1.8.1

has the fix that prevents that in future 👍