ci(release-parity): add build headroom; tidy the 0.10.1 changelog opening

release-parity.yml: the headroom trace added in 6fcbc92e9 showed the test
build using all memory and swap on the runner (peak "mem used 15574/15989 MiB
swap used 3052/3071 MiB", job 110549112727 on 2c95b7de7), which accounts for
the runner shutting this job down (exit 143) on earlier candidates. The job
now runs the same headroom step ci.yml's test lane uses: remove unused
preinstalled SDKs and add an 8 GiB swapfile. Tests, flags and profile are
unchanged. release.yml calls this workflow after the tag, so the tagged tree
carries the step.

CHANGELOG.md: the 0.10.1 section opened with a website item and called the
release a "source candidate"; that text is the release body. The summary now
leads and the website item is a bullet under Changed (credit unchanged).
docs/INSTALL.md: one stale example date removed.

No Rust source changes. actionlint passes on release-parity.yml;
scripts/test_ci_migration_wiring.py OK; sync-changelog.sh --check: up to
date; check-contributor-credit.py: every contributor credited. The new step is
not yet run hosted.

Signed-off-by: CodeWhale Bot <[email protected]>
This commit is contained in:
CodeWhale Bot committed 2026-10-01 13:20:38 -07:00
1 parent 5adddd22ac
commit 3665adde81
4 files changed
+29 -15

No files matched your search

+18
View File
@@ -80,6 +80,24 @@ jobs:
-A clippy::uninlined_format_args \
-A clippy::too_many_arguments \
-A clippy::unnecessary_map_or
- name: Build headroom
# The headroom trace below showed this job's test build using all of
# the runner's memory and swap (15574/15989 MiB and 3052/3071 MiB on
# 2c95b7de7), which is how the runner came to shut it down on earlier
# candidates. Same step as ci.yml's "Ubuntu build headroom": drop
# preinstalled SDKs this job never uses and add swap. release.yml
# calls this workflow after the tag, so the tagged tree needs it too.
shell: bash
run: |
df -h / /mnt; free -m
sudo rm -rf /usr/share/dotnet /usr/local/lib/android /opt/ghc /usr/local/.ghcup /opt/hostedtoolcache/CodeQL
if sudo fallocate -l 8G /mnt/cw-swapfile && sudo chmod 600 /mnt/cw-swapfile \
&& sudo mkswap /mnt/cw-swapfile >/dev/null && sudo swapon /mnt/cw-swapfile; then
echo "Added 8 GiB swap at /mnt/cw-swapfile"
else
echo "::warning::Could not add swap; continuing with the runner default"
fi
df -h / /mnt; free -m
- name: Workspace tests
# Same test binaries as `cargo test`, run by cargo-nextest: one process
# per test. This gate used libtest, where every test shares one process,
+5 -7
View File
@@ -9,18 +9,16 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
## [0.10.1] - 2026-10-01
The website's not-found page now uses the Codwhale poster and typo joke,
with English/Chinese recovery links to home and docs
([#6419](https://github.com/Hmbown/Codewhale/issues/6419),
[#6420](https://github.com/Hmbown/Codewhale/pull/6420)).
Codewhale v0.10.1 source candidate focuses on reliability and first-run behavior.
Turns that
Codewhale v0.10.1 focuses on reliability and first-run behavior. Turns that
stall now say so, approvals keep what you approved, plugin suggestions are
quieter, and Fleet runs can be checked before they spend anything.
### Changed
- The website's not-found page now uses the Codwhale poster and typo joke,
with English/Chinese recovery links to home and docs
([#6419](https://github.com/Hmbown/Codewhale/issues/6419),
[#6420](https://github.com/Hmbown/Codewhale/pull/6420)).
- Script tools can no longer approve themselves or replace built-in tools
(founder decision D4). A `# approval: auto` line in a script under
`~/.codewhale/tools` (or `[tools].plugin_dir`) is ignored: the tool follows
+5 -7
View File
@@ -9,18 +9,16 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
## [0.10.1] - 2026-10-01
The website's not-found page now uses the Codwhale poster and typo joke,
with English/Chinese recovery links to home and docs
([#6419](https://github.com/Hmbown/Codewhale/issues/6419),
[#6420](https://github.com/Hmbown/Codewhale/pull/6420)).
Codewhale v0.10.1 source candidate focuses on reliability and first-run behavior.
Turns that
Codewhale v0.10.1 focuses on reliability and first-run behavior. Turns that
stall now say so, approvals keep what you approved, plugin suggestions are
quieter, and Fleet runs can be checked before they spend anything.
### Changed
- The website's not-found page now uses the Codwhale poster and typo joke,
with English/Chinese recovery links to home and docs
([#6419](https://github.com/Hmbown/Codewhale/issues/6419),
[#6420](https://github.com/Hmbown/Codewhale/pull/6420)).
- Script tools can no longer approve themselves or replace built-in tools
(founder decision D4). A `# approval: auto` line in a script under
`~/.codewhale/tools` (or `[tools].plugin_dir`) is ignored: the tool follows
+1 -1
View File
@@ -23,7 +23,7 @@ there.
Install commands that use `latest` resolve to the latest **published** GitHub
Release or package. Between releases, `main` may already describe the next
version (for example the v0.10.1 source candidate before 2026-09-28). A
version (for example a v0.10.1 source candidate before its tag). A
candidate isn't installable until its tag, checksums and release assets
exist.