Development record
04-launch.md:664-666 and commands/launch.md:1062-1064 say auto-release.yml renders the plugin archive on the pushed commit (the command page: 'in detect') before the tag; auto-release.yml runs no launch archive, and the CI renders are release.yml's verify (.github/workflows/release.yml:205) and release job (:545), as adr-2609231048308186:71-73 and 04-launch.md:139-142 say. Resolved iss-2609260552247395 fixed the same claim at commands/launch.md:152-153 only
issueopenminoriss-2610252214271250
04-launch.md:664-666 and commands/launch.md:1062-1064 say auto-release.yml renders the plugin archive on the pushed commit (the command page: 'in detect') before the tag; auto-release.yml runs no launch archive, and the CI renders are release.yml's verify (.github/workflows/release.yml:205) and release job (:545), as adr-2609231048308186:71-73 and 04-launch.md:139-142 say. Resolved iss-2609260552247395 fixed the same claim at commands/launch.md:152-153 only
Frontmatter
| id | iss-2610252214271250 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610252214271250-04-launch-md-664-666-and-commands-launch.md
open on GitHub ↗ · commit history ↗
mentions2
- adr-2609231048308186The catalog pins the latest release's plugin archive
- iss-2609260552247395commands/launch.md:152-153 tells a user that a failed release shows up as auto-release's detect job failing on the archive-pin gate, but auto-release runs no `launch archive` since 2026-09-25: the gate is release.yml's verify job, so the page sends the reader to the wrong job. Found by the v0.11.0 brief-surface cross-check (x-007).