release-new-version
Prepare Anarlog Nightly builds and promote tested desktop stable versions with current CLI, local and hosted MCP, API, agent packages, and documentation. Deploy any required hosted services during the release. Validate and merge release updates before publishing. Distribute mobile builds when requested.
modem-dev · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add modem-dev/ossrules --skill release-new-versionAbout this skill
name: release-new-version description: Prepare Anarlog Nightly builds and promote tested desktop stable versions with current CLI, local and hosted MCP, API, agent packages, and documentation. Deploy any required hosted services during the release. Validate and merge release updates before publishing. Distribute mobile builds when requested. metadata: internal: true
Release a New Version
Use this for Nightly builds, stable desktop releases, and requested mobile store distribution. A stable desktop release must come from main, after the changelog and required CLI, MCP, API, agent-package, and documentation updates are accurate, validated, and merged. Desktop and watchOS share the marketing version in release-version.json. iOS and Android use apps/mobile/release-version.json. Platform build numbers and publication schedules remain independent.
Core Rule
Do not trigger a stable release from an unmerged branch. Complete the release surface review and changelog below, merge the required changes to main, then freeze the candidate and release that merged commit through its Nightly tag.
Nightly and Stable Operations
- Existing users and the main download remain on stable. Nightly is an explicit separate-app install, with its own updater feed and CLI command. It opens the same local database as stable; settings, store, and sign-in stay per app.
- The team uses Nightly for daily meetings. Volunteers can join through the announcement in the next stable changelog and product-update newsletter.
.github/workflows/desktop_nightly.yamlruns daily at 15:00 UTC (midnight KST) and can be dispatched manually frommain. It runs desktop JS/i18n and native CI, including source CloudSync rebuilds, before building and publishing all desktop platforms throughdesktop_cd.yamlwithchannel=nightly.- Nightly versions are
<shared-version>-nightly.<n>, where<n>counts up from 1 for each base version (1.4.24-nightly.1,1.4.24-nightly.2, ...) and resets whenrelease-version.jsonmoves to the next stable. Each build snapshotspackages/changelog/nightly.mdinto the app and a GitHub prerelease taggeddesktop_nightly_v<nightly-version>. Maintain that file as curated, user-facing changes since the previous stable release; do not generate a raw commit dump. Nightly notes never belong in the website's stable changelog. - Target weekly ordinary stable releases. Select a published Nightly commit, pin the team's app to it for 2–3 working days, and record real meeting results. Disable automatic updates while testing that candidate. CI or elapsed time alone is not evidence of use. Confirm recording/transcription, saved notes after restart, sync, and stable-to-candidate upgrades on shipped platforms.
- One release owner records the candidate, Nightly release/run, testing results, unresolved issues, and go/no-go decision in the release task. A serious regression postpones publication. Candidate fixes require renewed affected testing; newer main features wait for the next candidate.
- Nightly and stable are separate signed packages. Build stable from the tested commit and verify its install/upgrade behavior before publication; do not present the Nightly binary as byte-identical to the stable artifact.
- For an urgent stable hotfix, start from the latest stable tag, carry the
minimal fix into main, and verify the patch. Record the owner's explicit
exception to the usual Nightly testing period; do not bundle unrelated work.
The candidate must still be merged into main before publication. If main has
advanced, dispatch
desktop_cd.yamlwithchannel=nightlyon the merged hotfix branch, supplying its exact SHA, then use the resulting Nightly tag for stable verification and publication. This preserves the minimal patch. - Shared APIs and synced data must stay compatible with existing stable clients.
Nightly and stable write the same local database, and the apps refuse to run
at the same time. A
-- breakingmigration published in Nightly locks stable users out of their notes until stable ships it: keep schema changes additive (see the rootAGENTS.md), and land a breaking migration only in the candidate that becomes the next stable release, so the lockout ends when that release publishes.
Publish and verify Nightly
gh workflow run desktop_nightly.yaml --ref main
gh run list --workflow desktop_nightly.yaml --limit 5
Verify the exact SHA and all called jobs, not only the aggregate status. A failed
run needs a fresh dispatch. Confirm the GitHub prerelease/tag, signed installers,
CrabNebula nightly downloads, and every platform's Nightly update response.
Install the published build and exercise Nightly-to-Nightly updating, auth,
sharing links, and the embedded CLI. Confirm stable remains on the stable feed.
The first published Nightly needs this verification before announcing it.
Do not send the newsletter or announce Nightly as available until the Nightly
builds, update feed, and https://anarlog.so/download/nightly/ are live and verified.
Use the newsletter skill for the announcement.
Nightly publication does not publish a website changelog or submit to stores.
Scope Boundary
Establish the exact desktop version and requested mobile destination before dispatching. A desktop release includes its existing Microsoft Store workflow; it does not imply mobile submission. When mobile is requested, distinguish TestFlight and Google Play internal testing from public App Store review and Google Play production rollout. Honor authorization already given in the task; do not ask again for an approved destination.
App Store here means the iOS app. The repository deliberately has no Mac App Store release lane; do not recreate one as part of a desktop or mobile release.
Every desktop release includes the CLI, local and hosted MCP, API, agent-package, and document
Read the complete source ↗