This PR introduces a script that automates checking whether major downstream repositories have been updated for a new toolchain release. Sample output: ``` % ./release_checklist.py v4.16.0-rc1 Repository: Batteries ✅ On compatible toolchain (>= v4.16.0-rc1) ✅ Tag v4.16.0-rc1 exists Repository: lean4checker ✅ On compatible toolchain (>= v4.16.0-rc1) ✅ Tag v4.16.0-rc1 exists Repository: doc-gen4 ✅ On compatible toolchain (>= v4.16.0-rc1) ✅ Tag v4.16.0-rc1 exists Repository: Verso ❌ Not on target toolchain (needs ≥ v4.16.0-rc1, but main is on leanprover/lean4:v4.15.0) Repository: ProofWidgets4 ✅ On compatible toolchain (>= v4.16.0-rc1) Repository: Aesop ✅ On compatible toolchain (>= v4.16.0-rc1) ✅ Tag v4.16.0-rc1 exists Repository: import-graph ✅ On compatible toolchain (>= v4.16.0-rc1) ✅ Tag v4.16.0-rc1 exists Repository: plausible ✅ On compatible toolchain (>= v4.16.0-rc1) ✅ Tag v4.16.0-rc1 exists Repository: Mathlib ✅ On compatible toolchain (>= v4.16.0-rc1) ✅ Tag v4.16.0-rc1 exists Repository: REPL ❌ Not on target toolchain (needs ≥ v4.16.0-rc1, but master is on leanprover/lean4:v4.14.0) ``` |
||
|---|---|---|
| .. | ||
| lib | ||
| apply.lean | ||
| collideProfiles.lean | ||
| diff_changelogs.py | ||
| gen_constants_cpp.py | ||
| gen_tokens_cpp.py | ||
| issues_summary.sh | ||
| mathlib-bench | ||
| patch.sh | ||
| prepare-llvm-linux.sh | ||
| prepare-llvm-macos.sh | ||
| prepare-llvm-mingw.sh | ||
| rebase-stage0.sh | ||
| reformat.lean | ||
| release_checklist.py | ||
| release_notes.py | ||
| release_repos.yml | ||