From 19c13bf382399a52d7b7ef13f6e086231aa56c2b Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Tue, 17 Nov 2026 15:05:38 -0800 Subject: [PATCH 1/2] chore(quest): claim quest/m0/daily-release.md Quest-Claim: a804ef2fb6f38f8d From e1857350e891b04f69bac4527272121aaea8a6ba Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Tue, 17 Nov 2026 15:07:47 -0800 Subject: [PATCH 2/2] ci(release)!: cut releases daily instead of on every merge Co-Authored-By: Claude Sonnet 5.5 --- .github/workflows/release.yml | 20 ++++++------- CONTRIBUTING.md | 16 ++++++----- SETUP.md | 4 +-- quest/m0/daily-release.md | 53 ----------------------------------- 4 files changed, 21 insertions(+), 72 deletions(-) delete mode 100644 quest/m0/daily-release.md diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index ebcdb47f..f28b856d 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -1,16 +1,16 @@ name: Release -# Every run on `main` (each push, a daily schedule, or a manual run) compares -# `main` with the latest published release, and cuts the next one when that -# range changes what ships. It builds and checks every binary first, then -# uploads them to a draft release and publishes it, which creates the tag, so -# no tag exists without its complete release. A failed or cancelled run needs -# no recovery: the next run sees the same unreleased range and replaces any -# draft it left. Pull requests that change what ships, and manual runs on other -# branches, only build and check. scripts/release-plan.sh holds both decisions. +# A run on `main` (the daily schedule, or a manual one) compares `main` with +# the latest published release, and cuts the next one when that range changes +# what ships, so a day's merges become one release and an urgent fix ships +# early with `gh workflow run release.yml --ref main`. A push to `main` cuts +# nothing. A run builds and checks every binary first, then uploads them to a +# draft release and publishes it, which creates the tag, so no tag exists +# without its complete release. A failed or cancelled run needs no recovery: +# the next run sees the same unreleased range and replaces any draft it left. +# Pull requests that change what ships, and manual runs on other branches, only +# build and check. scripts/release-plan.sh holds both decisions. on: - push: - branches: [main] pull_request: schedule: - cron: "17 6 * * *" diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 410ad936..f1bbcc4a 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -51,13 +51,15 @@ The package stays `private`; GitHub releases will ship the `quest` binary. ## Releases -The Release workflow cuts every release; no person or agent tags one. Each -push to `main`, a daily schedule, and a manual run on `main` compare `main` -with the latest published release, and cut the next one when that range -changes what ships, as `scripts/release-plan.sh` decides: everything the -binaries and the flake package build from, every file Release publishes, and -the workflows that build and check them. Its pull request runs use the same -predicate to decide whether to build. The next version is greater than every +The Release workflow cuts every release; no person or agent tags one. A daily +schedule (06:17 UTC) and a manual run on `main` compare `main` with the latest +published release, and cut the next one when that range changes what ships, so +a day's merges become one release and a day with none cuts nothing. A push to +`main` cuts no release; an urgent fix ships early once it merges, with +`gh workflow run release.yml --ref main`. `scripts/release-plan.sh` judges the +range: everything the binaries and the flake package build from, every file +Release publishes, and the workflows that build and check them. Its pull +request runs use the same predicate to decide whether to build. The next version is greater than every `vX.Y.Z` tag: a minor bump (a major one from 1.0) when a commit subject in the range has `!` before its colon, a patch bump otherwise. diff --git a/SETUP.md b/SETUP.md index 24277412..b133b6a8 100644 --- a/SETUP.md +++ b/SETUP.md @@ -12,8 +12,8 @@ line in its root instructions. ## Install and pin Pin the latest [release](https://github.com/moq-dev/quest/releases) tag. -Every merge that changes what Quest ships becomes a release, so a release tag -is never far behind `main`; prefer it to pinning a commit. +A day's merges that change what Quest ships become one release, cut daily, so a +release tag is at most about a day behind `main`; prefer it to pinning a commit. Releases ship binaries for macOS, Linux, and native Windows on arm64 and x64. Never pin v0.1.0: it has no Windows archives and no `quest worktree hook` command, which `quest init`'s Claude Code hooks call. Every later release has diff --git a/quest/m0/daily-release.md b/quest/m0/daily-release.md deleted file mode 100644 index 9ca4a235..00000000 --- a/quest/m0/daily-release.md +++ /dev/null @@ -1,53 +0,0 @@ -# [S] Release once a day instead of on every merge - -## Goal - -Quest cuts at most about one release a day, so each repository that pins it gets -about one bump PR a day instead of four to eight, while an urgent fix can still -reach consumers within the hour through a manual dispatch of Release. Pushes to -`main` no longer cut releases; the daily schedule cuts whatever shipping changes -have piled up since the latest release, and skips the day when none have. - -Non-goals: the version rule (before 1.0, a breaking `!` commit bumps the minor -version) stays as it is, and 1.0 and the public release stay -[m1](/quest/m1/README.md)'s. - -## Plan - -Decided 2026-11-17 (maintainer, /quest-plan), after asking why quest had so -many minor versions and whether to adopt moq-dev/moq's `release` branch. Since -#688 and #717 (decided 2026-11-12), every shipping merge cut a release: 41 -releases from 2026-11-13 to 2026-11-17, v0.8.0 to v0.22.0, and about 200 -`bump quest` PRs across 11 consumer repositories (33 in moq-dev/moq.dev, 28 in -kixel-ai/rust2, 19 in moq-dev/moq), each running that repository's CI and -taking its merge queue. The minor bumps come from AGENTS.md's no-compatibility -rule, which makes most feature PRs `feat!:`; the number itself is cosmetic -before 1.0, so the churn is what this quest cuts. - -- What does this cut? ✅ Releases, and so consumer bump PRs (rejected: only the - version numbers, such as `!` bumping the patch version before 1.0, which - leaves the bump churn; gating releases on more checks). -- How are releases batched? ✅ A daily cut from `main` on Release's existing - 06:17 UTC schedule, with pushes to `main` no longer releasing (rejected: a - moq-dev/moq-style `release` branch, which exists there to run an expensive - optional gate before publishing many packages, while quest has one artifact - that Release already builds and checks before publishing, so a second branch, - ruleset, and cut PR add process and catch nothing new; the watcher - debouncing bumps, which keeps the release churn and puts the fix in host - configuration). This supersedes 2026-11-12's "a release, cut on every merge - that changes what ships" from #688; consumers still pin a release, and the - watcher's bump pass still follows the latest one. -- How does an urgent fix ship early? ✅ Manual dispatch only: - `gh workflow run release.yml --ref main` after the fix merges, by the - maintainer or the agent that lands it (rejected: a `release-now` PR label that - releases on its push; releasing on any `fix:` commit, since many fixes are - internal and the churn would creep back). -- ✅ m0: the churn lands on moq-dev's repositories' merge queues and CI now - (rejected: m1). - -Release's pull request runs keep building and checking what ships, so a push -to `main` needs no build of its own. `scripts/release-plan.sh` decides the same -way; only the triggers change. Update CONTRIBUTING.md's Releases section and -SETUP.md's "Every merge that changes what Quest ships becomes a release" to the -daily cut and the dispatch, and the comments at the top of `release.yml`; this -quest is the maintainer's request to edit CONTRIBUTING.md.