diff --git a/README.md b/README.md index e1bda545..b705e0d3 100644 --- a/README.md +++ b/README.md @@ -82,8 +82,7 @@ bun link With Nix, `nix run github:moq-dev/quest -- --help` builds and runs it instead. Native Windows needs no WSL for Quest: see [installation and removal](docs/windows.md). -Windows ZIP artifacts are added by the next release containing this change; -older releases remain macOS/Linux-only. +Releases from v0.3.0 on ship Windows ZIPs; v0.1.0 is macOS/Linux-only. The [CSV export example](examples/export/quest/README.md) is a small, working quest tree. From this checkout: diff --git a/SETUP.md b/SETUP.md index 209d3807..506a7e27 100644 --- a/SETUP.md +++ b/SETUP.md @@ -15,12 +15,9 @@ 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. Releases ship binaries for macOS, Linux, and native Windows on arm64 and x64. -Check that the chosen release includes the Windows archives and the -`quest worktree hook` command that `quest init`'s Claude Code hooks call; -v0.1.0 has neither, so until a later release exists treat it as no release. If there is no -release yet and the repository uses a nix flake (not on Intel Macs), pin the -latest commit on `main`, which the flake builds from source; otherwise tell the -user Quest has no release to install yet and stop. +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 +both. Use the tool manager the repository already has: diff --git a/docs/windows.md b/docs/windows.md index 9262cb88..a63e5d94 100644 --- a/docs/windows.md +++ b/docs/windows.md @@ -11,9 +11,8 @@ Bun requires [Windows 10 version 1809 or later](https://bun.sh/docs/installation and an x64 processor with SSE4.2; ARM64 uses its native build. The release and core/lifecycle CI use [Windows Server 2022 x64 and Windows 11 ARM64 runners](https://docs.github.com/en/actions/reference/runners/github-hosted-runners). -This change adds Windows artifacts to the next release containing it. Existing -releases such as v0.1.0 do not contain them. Choose an actual published tag -with the matching ZIP before installing. See the [release list](https://github.com/moq-dev/quest/releases). +Releases from v0.3.0 on ship the Windows ZIPs; v0.1.0 does not. See the +[release list](https://github.com/moq-dev/quest/releases). ## Install diff --git a/quest/m0/pin-bumps/follow-release.md b/quest/m0/pin-bumps/follow-release.md index cf010b33..02490cd7 100644 --- a/quest/m0/pin-bumps/follow-release.md +++ b/quest/m0/pin-bumps/follow-release.md @@ -24,7 +24,3 @@ Key a target's recorded bump on the release it moved to, not the base head the watcher passes in: otherwise a pass that runs before the Release workflow tags the base records the target done, and the release that follows is skipped until `main` moves again. Update README.md's "Pin bumps" section to match. - -## Required - -- [Check the first automated release](/quest/m0/pin-bumps/release.md) - a published release for a bump to follow diff --git a/quest/m0/pin-bumps/release.md b/quest/m0/pin-bumps/release.md deleted file mode 100644 index 61470e70..00000000 --- a/quest/m0/pin-bumps/release.md +++ /dev/null @@ -1,31 +0,0 @@ -# [XS] Check the first automated release - -## Goal - -The first release the Release workflow cuts on its own is complete and -installable, and the docs stop treating v0.1.0 as the only release. - -## Plan - -[moq-dev/quest#708](https://github.com/moq-dev/quest/pull/708) made the -Release workflow cut a release for every merge to `main` that changes what -ships (see CONTRIBUTING.md's Releases section), as decided 2026-11-12 on the -[epic](/quest/m0/pin-bumps/README.md). Its first release exists only after that -PR merges. Once it does, check it: - -- The release lists both Windows ZIPs that SETUP.md expects, beside the - macOS/Linux tarballs, `SHA256SUMS`, and `quest-installer.sh`. -- Every job of the run's Install check passed. A failure ships its fix as the - next release; fix it here and check that release instead. -- The release binary has `quest worktree hook`, the Goal of - [the v0.2.1 cut](https://github.com/moq-dev/quest/blob/2a80c902/quest/m1/release.md): - `quest worktree hook --help` exits 0. - -Then drop SETUP.md's v0.1.0 caveat and the "next release" notes in README.md -and docs/windows.md, and delete this quest. - -## Waiting - -- moq-dev/quest: the Release workflow publishes its first automated release - after #708 merges; check that `gh release list --repo moq-dev/quest` shows a - release newer than v0.1.0, or run the Release workflow on `main` by hand.