You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tracks the v0.5.0 release (the security release, epic #286), at dev @ 3c85772.
Local runs: run_tests.sh on gcc-15, clang-22, gcc-16, clang-22-asan and gcc-16-asan; the full --baseline snippet runs (GCC 15, Clang 22, GCC 16); links, the index, the Core Guidelines index, check_workflows.py, evals/check.py, and run_clang_tidy.sh
Every failure fixed through the fix loop, and the failed workflows re-run green
docs/platform-support.md, the toolchain pages and the notes regenerated from the release run, with every notes claim re-checked and a "Notes claims" table in the release PR
docs/releases/v0.5.0.md and the version bump
Default branch is main
Owner's approval → release PR dev → main → tag v0.5.0 → GitHub release
Known open issues to list: #337–#345 (from the v0.4.0 run), #351, #354, and the vendor drafts.
CI: three consented all.yml runs on dev, and every job is green in its newest run:
41657155620 at 3c85772, every platform;
41689101415 at 3835b98, the 43 failed jobs only;
41707574171 at 86f6c76, the last 4.
Overall: 59 toolchain jobs with 0 test failures, plus the clang-tidy and fuzz jobs.
Fixes found by the runs:#366, #367, #372–#375, #381–#383, #385, #386. Each had an issue and was merged on the owner's review. Also #377, the CI jobs input that made the fix-up runs possible.
Local at 86f6c76:
tests: gcc-15, clang-22, gcc-16 and both ASan presets, 0 failures;
snippets: 0 new failures on all three compilers;
links, index, workflows, evals (31/8/9) and clang-tidy: all pass.
Report and notes: the report is regenerated from the three runs plus the local results (--check clean). The platform support notes were re-derived claim by claim; the claims table is in #388.
Next: the owner's review of #388, then the owner's release approval, the release PR dev → main, the tag and the GitHub release. The default branch is main.
Notes PR #388 merged into dev (81cc1d35). Release PR: #389 (main ← dev, head 81cc1d3), title and description written. Next: the owner's merge verdict on #389, then the v0.5.0 tag on its merge commit and the GitHub release.
v0.5.0 re-released with tools/release_notes.py (#390, #391) at the owner's request (#392): release PR #394 merged into main (bb8bd634), the tag now points there, and the GitHub release was regenerated. The first tag (f97b4608) is the same release without the script.
Activity
homer6 commentedon Nov 3, 2026
All.yml run 41657155620 on dev 21505ad: 20 passed, 43 failed.
Code problems, each with an issue and a fix PR awaiting review:
nulis a reserved name on Windows (all 8 Windows jobs).<stdckdint.h>is C-only (2 FreeBSD jobs).Cfenv.RoundingModesfails in the GCC 16 hardened job (-O2 x86-64rintexpansion).Outages, not code:
curl: (6) Could not resolve host: apt.llvm.orgat the toolchain step (every apt.llvm.org Clang job, plus the clang-tidy and fuzz jobs).ENOTFOUND; its snippets were baseline-only.After the fixes merge, these workflows need a re-run on dev: linux, macos, windows-msvc, windows-gnu and freebsd.
homer6 commentedon Nov 3, 2026
Release checks done; notes PR: #388.
CI: three consented
all.ymlruns ondev, and every job is green in its newest run:3c85772, every platform;3835b98, the 43 failed jobs only;86f6c76, the last 4.Overall: 59 toolchain jobs with 0 test failures, plus the clang-tidy and fuzz jobs.
Fixes found by the runs: #366, #367, #372–#375, #381–#383, #385, #386. Each had an issue and was merged on the owner's review. Also #377, the CI
jobsinput that made the fix-up runs possible.Local at
86f6c76:Report and notes: the report is regenerated from the three runs plus the local results (
--checkclean). The platform support notes were re-derived claim by claim; the claims table is in #388.Next: the owner's review of #388, then the owner's release approval, the release PR dev → main, the tag and the GitHub release. The default branch is
main.homer6 commentedon Nov 3, 2026
Notes PR #388 merged into
dev(81cc1d35). Release PR: #389 (main ← dev, head81cc1d3), title and description written. Next: the owner's merge verdict on #389, then thev0.5.0tag on its merge commit and the GitHub release.homer6 commentedon Nov 4, 2026
Released. #389 merged into
main(f97b4608), tagv0.5.0on that commit, GitHub release: https://github.com/homer6/cpp-docs/releases/tag/v0.5.0. Every checklist item is done.homer6 commentedon Nov 4, 2026
v0.5.0 re-released with
tools/release_notes.py(#390, #391) at the owner's request (#392): release PR #394 merged intomain(bb8bd634), the tag now points there, and the GitHub release was regenerated. The first tag (f97b4608) is the same release without the script.