Skip to content

macOS app: build number from VERSION so Sparkle can offer updates - #452

Merged
AVADSA25 merged 2 commits into
mainfrom
bundle-version
Oct 8, 2026
Merged

AVADSA25 merged 2 commits into
mainfrom
bundle-version

Conversation

@AVADSA25

@AVADSA25 AVADSA25 commented Oct 8, 2026

Copy link
Copy Markdown
Owner

What

Sparkle decides whether an update is newer from CFBundleVersion (the appcast's sparkle:version). Every build so far had CFBundleVersion = 1 (the published 3.2.0 appcast too), so an installed copy would never be offered 3.6.0. build_app.sh now sets CFBundleVersion from VERSION along with CFBundleShortVersionString; the static Info.plist matches VERSION (3.6.0).

Needed before publishing the 3.6.0 update (Mickael, 8 Oct: "publish the update and buyer link"). The 3.6.0 app must be rebuilt, re-signed and re-notarized after this.

Checks

  • tests/test_app_bundle.py: new test builds the bundle and checks both version keys equal VERSION; negative control on main: fails. Bundle, packaging and release tests: 17 passed.

🤖 Generated with Claude Code

Mikarina13 and others added 2 commits October 8, 2026 16:33
Sparkle compares CFBundleVersion (the appcast's sparkle:version), not the short
version string. It stayed "1" on every build (3.1.0 through 3.6.0), so an
installed copy was never offered a newer release. build_app.sh now sets
CFBundleVersion from VERSION alongside CFBundleShortVersionString, and the
static Info.plist matches VERSION (3.6.0).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@AVADSA25
AVADSA25 merged commit 80e34af into main Oct 8, 2026
1 check passed
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.

2 participants