How do I bump the project version?
The version bump is housekeeping that always accompanies Open a new sprint. Land it as a separate commit on the same sprint-open PR.
Question
How do I bump ORE Studio's project version across every file that mentions it?
Answer
Five files carry the version string. Edit them as a single commit.
- Pick the new version. The project follows
0.0.<N>whereNtracks the sprint number; bumpNby one. Top-level
CMakeLists.txt:-project(OreStudio VERSION 0.0.<OLD> LANGUAGES CXX +project(OreStudio VERSION 0.0.<NEW> LANGUAGES CXX
vcpkg.json:- "version-string": "0.0.<OLD>", + "version-string": "0.0.<NEW>",
The three GitHub workflow package filenames under
.github/workflows/:continuous-linux.yml—orestudio_0.0.<OLD>_amd64.debcontinuous-macos.yml—OreStudio-0.0.<OLD>-Darwin.dmgcontinuous-windows.yml—OreStudio-0.0.<OLD>-win64.*
Each is a single
sed-able substitution.readme.org— four things:a. The sprint badge (line 25): update both the
Sprint-<N>label and the href linksprint_<N>/sprint.htmlto the new sprint number:-<a href="...sprint_<OLD>/sprint.html"><img ... src=".../Sprint-<OLD>-blue.svg"/></a> +<a href="...sprint_<NEW>/sprint.html"><img ... src=".../Sprint-<NEW>-blue.svg"/></a>
b. The "PRs since" static badge (line 43): update the label and the href's merged date filter to the new sprint start date. Use a static badge (
img.shields.io/badge/PRs%20since%20v0.0.<NEW>-GitHub%20search-blue); do not usebadge/dynamic/jsonwith a GitHub Search API URL — shields.io rejects theurlparameter when the inner URL contains query-string syntax:-<a href="...merged%3A%3E%3D<OLD-DATE>"><img alt="PRs since v0.0.<OLD>" src="...badge/PRs%20since%20v0.0.<OLD>-GitHub%20search-blue"/></a> +<a href="...merged%3A%3E%3D<NEW-DATE>"><img alt="PRs since v0.0.<NEW>" src="...badge/PRs%20since%20v0.0.<NEW>-GitHub%20search-blue"/></a>
c. The "commits-since" badge, which uses the previous version tag — so when bumping from
0.0.<OLD>to0.0.<NEW>, the commits-since badge moves fromv0.0.<OLD-1>tov0.0.<OLD>.d. The screenshot asset reference: if a new
assets/images/ore_studio-v0.0.<NEW>.pngscreenshot exists, update the prose reference to point to it.Verify. Sanity-check that nothing else mentions the old version:
grep -rn "0\.0\.<OLD>" \ CMakeLists.txt vcpkg.json .github/workflows readme.org
Expect zero matches.
- Commit as
[build] Bump version to 0.0.<NEW>on the sprint-open branch. No separate PR needed.
Script
No wrapper — the five files are touched manually because every release confirms the diffs by eye.
Tested by
CI builds the renamed package artefacts. If the workflow paths and the actual package name disagree, the artefact upload step fails on the post-build run.
See also
- How do I open a new sprint? — the sibling agile-side step.
- CMake setup — preset menu and project structure background.