Skip to content

RELEASING.md

Latest commit

 

History

History
74 lines (58 loc) · 2.39 KB

RELEASING.md

File metadata and controls

74 lines (58 loc) · 2.39 KB
Raw

Releasing Daisy

Daisy uses trunk development with a separate stable source line. Sparkle channels decide who receives a build; git branches record the source that made it.

  • main is the active product line and normally ships beta builds.
  • stable points to the source of the latest promoted stable build and is the base for stable hotfixes.
  • v<version> tags map every published build to its app source.

The website repository owns the distribution state:

  • public/appcast.xml is the Sparkle release history.
  • lib/latestVersion.ts points the main download CTA to stable.
  • lib/betaVersion.ts points opt-in users to the newest beta.
  • public/downloads/ keeps every referenced signed DMG.

scripts/release.sh finds daisy-web when it is the parent checkout or a lowercase sibling. Set DAISY_WEB_REPO=/absolute/path/to/daisy-web for any other layout. Read the current stable and beta versions from the generated files above; do not duplicate those values in this document.

1. Cut a beta

Start from a clean, tested main. The build number must be greater than every sparkle:version already in the appcast.

git switch main
DAISY_AUTO_PUSH=1 ./scripts/release.sh <version> <build> beta
git add Daisy.xcodeproj/project.pbxproj
git commit -m "<version> (b<build>)"
git push
git tag v<version>
git push origin v<version>

The script runs tests, archives, signs, notarizes, builds the DMG, publishes it to daisy-web, injects the beta appcast item, updates lib/betaVersion.ts, and commits the website. It never pushes the app repository.

2. Promote a soaked beta to stable

Promotion reuses the already signed beta DMG; it does not rebuild it.

DAISY_AUTO_PUSH=1 ./scripts/release.sh promote <version>
git switch stable
git merge --ff-only v<version>
git push
git switch main

The command removes the beta channel tag from the existing appcast item and updates lib/latestVersion.ts to the same artifact.

3. Ship a stable hotfix

git switch stable
git switch -c hotfix/<short-description>
# implement and verify the fix
DAISY_AUTO_PUSH=1 ./scripts/release.sh <version> <build> stable
git switch stable
git merge --ff-only hotfix/<short-description>
git tag v<version>
git push origin stable v<version>
git switch main
git merge stable

Always review both generated commits and verify the deployed download before announcing a release. Keep all historical DMGs referenced by the appcast.