KrishKrosh / KrishKrosh/TrackWeight

[Suggestion] Unify versioning scheme (SemVer) + keep Info.plist in sync

Open
#64 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Swift
Stars
9.1k
Forks
397
PR merge metrics
No merged PRs in 30d

Description

Hi! Love TrackWeight. I’d like to suggest adopting a consistent versioning scheme to make releases easier to understand and to help with debugging / packaging.

## Current situation:

Some releases use a timestamp-like version, e.g. `TrackWeight 20250727-023051`
Others use SemVer like `1.0.3`
`Info.plist` (CFBundleShortVersionString / CFBundleVersion) seems to stay at `1.0`/`1` across releases
This makes it hard to map installed apps / bug reports to a specific release.

## Suggestion
Use SemVer as the public version and keep everything in sync:

- Release tag/title/DMG name: vMAJOR.MINOR.PATCH
- CFBundleShortVersionString: MAJOR.MINOR.PATCH
- CFBundleVersion: monotonically increasing build number (or CI build number)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating Info.plist and the release or build configuration that supplies the app version, then compare those values with the existing release tags and DMG names. Done means the chosen SemVer and build-number scheme is defined and the release artifacts and CFBundleShortVersionString/CFBundleVersion stay synchronized.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, swift
Domain
build-system, release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.