Skip to content

chore: downstream-lean4 adaptations for nightly-2026-10-26 - #45345

Open
downstream-lean4[bot] wants to merge 2 commits into
leanprover-community:bump/v4.37.0from
leanprover:downstream-lean4-export
Open

downstream-lean4[bot] wants to merge 2 commits into
leanprover-community:bump/v4.37.0from
leanprover:downstream-lean4-export

Conversation

@downstream-lean4

Copy link
Copy Markdown
Contributor

This PR contains automatically exported adaptations up until leanprover/downstream-lean4@7602fe4.

If any dependencies have open export PRs themselves, you may need to merge them first and then run lake update in this PR. If this PR becomes outdated, just close it and a new one will be opened soon. No new export PRs will be opened while one is already open.

downstream-sha: 7602fe42a5d5f6c8e4da64b0779eecd959971dc1

downstream-sha: 7602fe42a5d5f6c8e4da64b0779eecd959971dc1
@github-actions github-actions Bot added the new-contributor This PR was made by a contributor with at most 5 merged PRs. Welcome to the community! label Oct 27, 2026
@github-actions

Copy link
Copy Markdown

Welcome new contributor!

Thank you for contributing to Mathlib! If you haven't done so already, please review our contribution guidelines, as well as the style guide and naming conventions. In particular, we kindly remind contributors that we have guidelines regarding the use of AI when making pull requests.

We use a review queue to manage reviews. If your PR does not appear there, it is probably because it is not successfully building (i.e., it doesn't have a green checkmark), has the awaiting-author tag, or another reason described in the Lifecycle of a PR. The review dashboard has a dedicated webpage which shows whether your PR is on the review queue, and (if not), why.

If you haven't already done so, please come to Zulip and join the Lean community.
Thank you again for joining our community.

@github-actions github-actions Bot added the increases-technical-debt Automatically added label for PRs which increase "strong" technical debts label Oct 27, 2026
@github-actions

github-actions Bot commented Oct 27, 2026 •

Copy link
Copy Markdown

PR summary 4fe22cd6b5

Import changes for modified files

No significant changes to the import graph

Import changes for all files
Files Import difference

Declarations diff (regex)

- dthen
- dthen_eq_then

You can run this locally as follows
## from your `mathlib4` directory:
git clone https://github.com/leanprover-community/mathlib-ci.git ../mathlib-ci

## summary with just the declaration names:
../mathlib-ci/scripts/pr_summary/declarations_diff.sh <optional_commit>

## more verbose report:
../mathlib-ci/scripts/pr_summary/declarations_diff.sh long <optional_commit>

The doc-module for scripts/pr_summary/declarations_diff.sh in the mathlib-ci repository contains some details about this script.

Declarations diff (Lean -- pending)

Computed after the build finishes.


Increase in strong tech debt: (relative, absolute) = (1.77, 0.23)
Current number Change Type (strong)
391 5 adaptation notes
26 1 disabled simpNF lints
11 2 disabled deprecation lints
No changes to weak technical debt.

Current commit 4fe22cd6b5
Reference commit 116662aa4c

This script lives in the mathlib-ci repository. To run it locally, from your mathlib4 directory:

git clone https://github.com/leanprover-community/mathlib-ci.git ../mathlib-ci
../mathlib-ci/scripts/reporting/technical-debt-metrics.py pr_summary
  • The relative value is the weighted sum of the differences with weight given by the inverse of the current value of the statistic.
  • The absolute value is the relative value divided by the total sum of the inverses of the current values (i.e. the weighted average of the differences).

mathlib-bors Bot pushed a commit that referenced this pull request Oct 27, 2026
`bump/*` branches now live in `mathlib4` rather than `mathlib4-nightly-testing`. PRs into them, such as the `downstream-lean4` export in #45345, depend on the `nightly-testing` branches of our dependencies. The "validate lake-manifest.json inputRevs" step in `build_template.yml` runs on these branches and fails them, though it used to be skipped when the branches were in the nightly-testing repo.

This PR skips the validation step when either of these starts with `bump/`:
- `github.ref_name`: pushes to `bump/*` branches, including the automation's `bump/nightly-*` branches.
- `github.base_ref`: PRs into a `bump/*` branch, from any repo.
(Note that `head_ref` is not read, so a PR from a branch starting with `bump/` can't get around this.)

Not covered: a non-`bump/*` branch pushed to mathlib4 with a PR into a bump branch. Push builds can't see the PR's base, so the check still runs there. (No one should be creating such branches and we have branch protection rules against this.)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

increases-technical-debt Automatically added label for PRs which increase "strong" technical debts new-contributor This PR was made by a contributor with at most 5 merged PRs. Welcome to the community!

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant