Skip to content

fix(release): sync Briefcase version with version.py and guard it#91

Merged
ErikChevalier merged 1 commit into
mainfrom
fix/release-version-sync
Jun 11, 2026
Merged

fix(release): sync Briefcase version with version.py and guard it#91
ErikChevalier merged 1 commit into
mainfrom
fix/release-version-sync

Conversation

@ErikChevalier

Copy link
Copy Markdown
Contributor

Problem

The 26.06.06 release built installers labelled 26.6.5: [tool.briefcase].version in pyproject.toml is mirrored separately from version.py and I bumped only version.py. The OS packages therefore carried the previous version, breaking the Linux .deb/.rpm upgrade path.

Fix

  • Bump [tool.briefcase].version to 26.06.06 to match version.py.
  • Add tests/test_version_consistency.py, which parses both and fails the build if they ever diverge, so this can't silently recur.

After merge: re-cut the v26.06.06 tag at the fixed commit so the GA installers carry the correct version.

🤖 Generated with Claude Code

The 26.06.06 release shipped installers still labelled 26.6.5 because the
[tool.briefcase] version in pyproject.toml is mirrored separately from
src/searchmob_desktop/version.py and was not bumped with it, so Briefcase
built the packages at the previous version and Linux package managers would
not treat them as an upgrade.

Bump the Briefcase version to 26.06.06 to match, and add
tests/test_version_consistency.py, which fails the build whenever the two
version strings drift, so this cannot silently recur.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@ErikChevalier ErikChevalier merged commit f78970d into main Jun 11, 2026
1 check passed
@ErikChevalier ErikChevalier deleted the fix/release-version-sync branch June 11, 2026 01:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant