Bump version v24.04.0a2 -> v24.04.0a3

[superstar54]

When specifying --minor with bumper update, it tries to increment the minor version part of the project's current version. However, v24.04.0a3 is not a valid next version based on the current versioning scheme.

Manually Specify the Next Version

Since the automatic minor update didn't work as intended, I used the --set-version flag to manually specify the next alpha version. This approach gives direct control over the version naming:

bumpver update --set-version v24.04.0a3 --dry

[superstar54]

@danielhollas I followed the wiki, but there is an error. Could you check the description of this PR. If you agree, I will update the wiki.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.85%. Comparing base (15abd2b) to head (b5ee81f).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #647   +/-   ##
=======================================
  Coverage   75.85%   75.85%           
=======================================
  Files          60       60           
  Lines        4312     4312           
=======================================
  Hits         3271     3271           
  Misses       1041     1041           

Flag	Coverage Δ
python-3.10	75.85% <100.00%> (ø)
python-3.9	75.88% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[danielhollas]

Yes, in the wiki the minor version bump was just an example. Here you want to bump the alpha version, not the minor version. bumbver has a special flag for that, I don't remember from the top of my head, please see bumpver update -h. Feel free to update the wiki with more examples.

[danielhollas]

@superstar54 I think you'll have to recreate the branch to get rid of the extra merge commit. You cannot squash/rebase here otherwise the tag would get lost.

[superstar54]

I think you'll have to recreate the branch to get rid of the extra merge commit. You cannot squash/rebase here otherwise the tag would get lost.

Do you mean to merge the branch to the main directly?

[danielhollas]

Yes, you will need to merge by creating a merge commit, otherwise you will loose the tagged commit.