version bump workflow doesn't calculate the version retroactively

[rmanaem]

It only uses the PR that releases the tool see:

Relevant commit: 751d981

It's respective workflow run: https://github.com/neurobagel/query-tool/actions/runs/13036084018/job/36366735131

TODO:

• find out why it is not looking at the other PRs
• change the wf so it computes the correct version by considering all previous PRs since the last release

[surchs]

Trying things out in #464, so far no luck. Probably should either open an issue or post on stackoverflow

[alyssadai]

@surchs, I know you mentioned trying some variants using the --dry-run option, but maybe this could be helpful?

intuit/auto#1490 (comment)

(also, did you mean to link a PR instead of this issue? :)

[surchs]

(also, did you mean to link a PR instead of this issue? :)

oh boy, that's worrying. Yes indeed I tried to to do that #490

[surchs]

Aha, yes indeed this was very useful, thanks @alyssadai. I learned that the canary release doesn't actually work:

⚠  warning   None of the plugins that you are using implement the `canary` command!

https://github.com/neurobagel/query-tool/actions/runs/13399686305/job/37427265986?pr=490#step:7:14

[surchs]

So we tried a lot of things on this issue. Our best guess is that we would need to use auto shipit --dry-run. However, auto does this thing called "context aware publishing" where it makes a canary release when run on a PR branch (as we are): https://intuit.github.io/auto/docs/generated/shipit

And as the error message above says, we can't make canary releases because of a plugin issue. So far it's not clear whether we are

• missing a plugin that enables canary
• have a plugin that is incompatible with canary

We tried removing plugins from the .autorc and the error message about canary stayed around. So most likely we are missing a plugin.

At this point the next step is to either

• open an issue / discussion on their GitHub
• ask on stackoverflow
• explore switching to a different tool that computes semver from labels (or maybe even does the release as well)

[surchs]

We'll keep this issue open an in tracked until we have an answer from opening an issue against auto or a post on stackoverflow