Summary
SnapDock currently uses manual SemVer versioning (MAJOR.MINOR.PATCH). While this is valid and compliant, the process is fully manual and not integrated with the build or release workflow. This issue proposes improving versioning discipline and automating release steps.
Problem
Manual versioning leads to:
- inconsistent bumping
- risk of forgetting to update version
- no automated changelog
- no automated tagging
- no CI‑driven release flow
- no link between commits and version numbers
This is outside the scope of #120, but should be addressed in a future milestone.
Goals
- Enforce SemVer bump rules
- Automate version bumping
- Automate changelog generation
- Automate Git tags
- Integrate versioning with CI
- Ensure version metadata is consistent across:
- package.json
- build artifacts
- release notes
- updater metadata
Non‑Goals
- No changes to artifact naming
- No changes to build section
- No changes to platform overrides
- No changes to signing
Notes
This issue is intentionally separate from build‑system cleanup to keep #120 focused and clean.
Summary
SnapDock currently uses manual SemVer versioning (
MAJOR.MINOR.PATCH). While this is valid and compliant, the process is fully manual and not integrated with the build or release workflow. This issue proposes improving versioning discipline and automating release steps.Problem
Manual versioning leads to:
This is outside the scope of #120, but should be addressed in a future milestone.
Goals
Non‑Goals
Notes
This issue is intentionally separate from build‑system cleanup to keep #120 focused and clean.