forked from heavy-duty/ceremony
38 lines
1.5 KiB
Markdown
38 lines
1.5 KiB
Markdown
# 0.6.2 — drill record
|
|
|
|
Measured 2026-08-24 on release PR !250, candidate branch
|
|
`build/231-release-0-6-2`. The release-path measurement was taken at
|
|
`fdb7d7577b4b30c11f2db9b47f278e2a16783c8c`; this record is the only later
|
|
candidate-tree change and `drills/` is outside the release path.
|
|
|
|
## Scope ruling — doors unchanged, no disposable-repo rehearsal
|
|
|
|
The last rehearsed tag is `0.6.1`. All three doors-unchanged conditions in
|
|
`drills/README.md` hold at this candidate tree:
|
|
|
|
1. `git diff 0.6.1..HEAD -- $(sh .github/scripts/release-path.sh)` changes
|
|
only the `CEREMONY_SELF_REF` pin in `.github/workflows/release.yml`, from
|
|
`0.6.1` to `0.6.2`. No release-door logic, decision, fact gathering,
|
|
version handling, changelog handling, or publish step changed.
|
|
2. The measured release path is exactly the output of
|
|
`.github/scripts/release-path.sh`:
|
|
|
|
```text
|
|
.github/workflows/release.yml
|
|
bin/
|
|
lib/version.sh
|
|
lib/decide.sh
|
|
lib/facts.sh
|
|
lib/changelog.sh
|
|
lib/forge.sh
|
|
```
|
|
|
|
3. `drills/0.6.1.md` records a full six-probe rehearsal. The Forgejo release
|
|
API reported `0.6.1` published at `2026-08-09T19:46:56Z`, neither draft nor
|
|
prerelease, and `origin/main:VERSION` read `0.6.2-dev`, confirming that main
|
|
was re-armed after that release.
|
|
|
|
A new disposable-repo rehearsal would therefore execute the same release-door
|
|
bytes as the full 0.6.1 rehearsal. This record asserts only the mechanically
|
|
checked doors-unchanged case; the release panel may still rule that a full
|
|
rehearsal is owed.
|