feat: add nightly release channel alongside stable#154
Merged
Conversation
- Add nightly builds from main via GitHub Actions (daily at 3am UTC) - Nightly runs as a separate app (com.silo.desktop.nightly), side-by-side with stable - Auto-generated version: 0.x.y-nightly.YYYYMMDD.githash - Configurable via tauri.nightly.conf.json and release-nightly.yml workflow - Document release channels in docs/guide and roadmap - Add ADR 0024 for release channels decision - Update CONTRIBUTING.md with release channel info - Add nightly_data_path() CLI command for nightly-specific data dirs - Expand user config tests for the new channel surface
- Format markdown tables to match Prettier's printWidth 80 rules - Restore .githooks/ pre-commit hook (deleted in PR #145) which auto-formats staged files with Prettier via lint-staged — this is the root cause of the recurring CI format failures - Also restore commit-msg hook for Conventional Commit enforcement
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Silo now has two release channels that run completely independently:
Stable
Traditional release-please flow: merged conventional commits feed a "release PR" that bumps versions, updates
CHANGELOG.md, tagssilo-vX.Y.Z, and triggers builds + publish of installers and the updater manifest.Nightly
Builds from
mainautomatically every day at 3am UTC via therelease-nightly.ymlworkflow. Nightly is a separate application (Silo Nightly, identifiercom.silo.desktop.nightly) that installs side-by-side with stable and uses its own data directories. The version string is auto-generated:0.x.y-nightly.YYYYMMDD.githash. The nightly GitHub Release is pinned to thenightlytag and overwritten on every build — release-please is not involved.Changes
.github/workflows/release-nightly.ymlapps/desktop/src-tauri/tauri.nightly.conf.jsonapps/desktop/src-tauri/src/commands/app_paths.rsnightly_data_path()CLI command, unified path logicapps/desktop/src-tauri/src/lib.rsCONTRIBUTING.mdapps/docs/roadmap.mdapps/docs/.vitepress/config.tsapps/docs/guide/release-channels.mddocs/decisions/0024-release-channels.mdpackages/extension-host/src/services/user-config.tsreleaseChannelon the user config surfacepackages/extension-host/src/services/user-config.test.tsNightly specifics
com.silo.desktop.nightlyinstalls alongside stable without conflictsilo-nightlyapplication/data directories (handled vianightly_data_path()CLI command)