You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have version...added ...changed and ... removed in the docs.
It would be good to test this in CI:
For all the mentioned versions, there is a tag.
Git pull tags shallow in case it is needed.
The version 0.0.0 is also ok. It will be renamed anyway for a release and is the one all new changes should use.
Problem: this should not fail on main just before a release tag is created, so maybe the tests just make sure that a new version directive has 0.0.0 in it or the test is skipped if on a release branch (main or (version).x)
It should also not fail if git is not present.
It looks quite simple but has a lot of constraints. What we want to avoid is a version directive in a PR that is added but fixes the version to something unreleased. The PR does not know about the future release.
A simple solution is preferred, not lots of code. It might not be feasable to test that.
Activity
github-actions commentedon Oct 25, 2026
Thanks for the issue, @niccokunzmann! A maintainer will review it shortly.
[-]Ceck version directives[/-][+]Check version directives[/+]