Skip to content

bump VERSION to v29.7.0-dev #7068

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
thaJeztah merged 1 commit into from
Jun 22, 2026
Merged

bump VERSION to v29.7.0-dev #7068

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion VERSION
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1 +1 @@
29.6.0
29.7.0

@docker-agent docker-agent Jun 22, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[MEDIUM] VERSION set to 29.7.0 instead of 29.7.0-dev as stated in the PR title

The PR title says "bump VERSION to v29.7.0-dev", but the file was changed to 29.7.0 (no -dev suffix).

The project's established pattern (visible in file history) is to append -dev to mark the development cycle after each release:

  • 29.6.0 → 29.5.3-dev → 29.5.2-dev → 29.5.1-dev …

Setting VERSION to 29.7.0 without -dev makes development builds appear to be a final stable release. This could cause version-detection tools, CI pipelines, or package managers to treat unreleased builds as 29.7.0 GA.

Expected: 29.7.0-dev
Actual: 29.7.0