leanprover-community / leanprover-community/physlib

Bump to version: v4.32.0

Open
#1,437 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Lean
Stars
749
Forks
189
Avg merge
1d 21h
Merged PRs (30d)
75

Description

Version bump

This issue is a tracker issue for bumping Physlib to new versions of Lean.
The checklist below should be used to ensure that the bump is done correctly.

Basics
  • Update mathlib rev in lakefile.toml.
  • Update doc-gen4 rev in lakefile.toml.
  • Remove the .lake file, e.g. on unix run rm -rf .lake.
  • Run lake update.
  • Check lean-toolchain updates correctly.
  • Update the Lean version badge in the README.md file.
Build
  • Run lake build and fix any errors.
Scripts
  • Ensure lake exe lint_all runs without errors.
  • Ensure lake exe TODO_to_yml mkFile runs without errors.
  • Ensure lake exe stats mkHTML runs without errors.
  • Ensure lake exe informal mkFile mkDot mkHTML runs without errors.
  • Ensure lake exe make_tag runs without errors.
  • Remove the created files rm ./docs/Informal.md; rm ./docs/InformalDot.dot; rm ./docs/InformalGraph.html; rm ./docs/Stats.html; rm ./docs/_data/TODO.yml.
Afterwards
  • Create a tag for the new version.
  • Put a bump notice on this thread.
Example past bumps

v4.20.0,
v4.20.0-rc5
v4.27.0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with lakefile.toml, lean-toolchain, and README.md, then review the linked past bump pull requests for the expected version changes. Remove .lake, run lake update and lake build, and run each listed lake executable to identify compatibility fixes. Done means all checklist commands pass, generated files are removed, the new tag is created, and the bump notice is posted.

Written by the indexing model from the issue text.

Assessment

Domain
build-system, release
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.