Skip to content

ci: derive the build number from the release version - #118

Merged
MegaManSec merged 1 commit into
mainfrom
ci-build-number-from-version
Sep 27, 2026
Merged

MegaManSec merged 1 commit into
mainfrom
ci-build-number-from-version

Conversation

@MegaManSec

Copy link
Copy Markdown
Owner

Summary

  • The release workflow's "Update version" step now sets CURRENT_PROJECT_VERSION to major*1000000 + minor*1000 + patch (for example 2.26.0 → 2026000), replacing agvtool next-version -all.
  • Previously agvtool bumped the committed build number but never committed it back, so every release shipped as build 3. The App Store requires build numbers that increase across uploads.
  • The version now reaches the script through an environment variable rather than being pasted into it.

As a ci: commit, this won't trigger a release.

agvtool next-version bumped the committed build number on every run without
committing it back, so every release shipped as build 3. The App Store needs
build numbers that increase across uploads, so set CURRENT_PROJECT_VERSION
to major*1000000 + minor*1000 + patch (2.26.0 -> 2026000), which always
grows with the version and maps back to its tag.
@MegaManSec
MegaManSec merged commit 5df84e3 into main Sep 27, 2026
2 checks passed
@MegaManSec
MegaManSec deleted the ci-build-number-from-version branch September 27, 2026 12:56
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 2.27.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant