I just had a look and the critical sentence seems to be "The Vagrantfile does not 
need to be updated for a bugfix release". I agree, this should no longer be 
necessary. Everything else should stay the same.

I think there is a also documentation to be updated. I'll make a change to the ReleaseWorkflow page, but it would be good if someone can double-check that the new information is correct.

Merged.

Given that you tested it and it did the right thing, feel free to merge.

Yes, I'd not change it retroactively. More work than it's worth.

Thanks for already solving it @malte. I tested it locally and it seems to work. I 
think we only want to change it for future releases, meaning we will not change 
the old vagrant files?

I've open a PR: https://github.com/aibasel/downward/pull/254 .

At first glance, it looks like we need to change two things.

In prepare-release.sh, we fill the Vagrant template like this:

fill_template "_Vagrantfile.tpl" "TAG" "$TAG" > $MAJOR/Vagrantfile.$MAJOR

Instead of the tag we want the branch. Something like this:

fill_template "_Vagrantfile.tpl" "BRANCH" "$BRANCH" > $MAJOR/Vagrantfile.$MAJOR


And then the template itself should use BRANCH instead of TAG, replacing

        git clone --branch TAG https://github.com/aibasel/downward.git downward

with:

        git clone --branch BRANCH https://github.com/aibasel/downward.git downward


(But this is not tested.)

Currently, our Vagrantfile hardcodes a specific bugfix release, requiring updates 
whenever a new bugfix release is available. This leads to unnecessary maintenance 
effort. Instead, we should modify the Vagrantfile to automatically use the latest 
bugfix release within a given branch, eliminating the need for manual updates.