ci: Auto-update the Lean toolchain and pinned deps - #83
Merged
Conversation
Runs daily and on demand. argumentcomputer/lean-update (dev, which carries
the pinned-tags support) bumps lean-toolchain to the latest stable release —
the updater's default channel; release candidates are opt-in via
release_channel — and moves plausible's pinned rev with it. The action opens
a PR on an update/lean-{release} branch whether or not the build passes, so
an incompatible release shows up as a failing PR to review rather than only
an issue. The PR is opened with a GitHub App token so that it triggers CI;
the same App as the org repo-sync workflows.
plausible's pin changes from the short hash 6304553 to v4.31.0 — the same
commit, since that hash is what the tag points at. Written as a version tag,
the pin is managed by the updater's defaults; a future deliberate pin to a
plain commit hash will be reported and left alone, pausing the automation
until the pin is back on a tag.
arthurpaulino
approved these changes
Aug 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Runs daily and on demand. argumentcomputer/lean-update (dev, which carries the pinned-tags support) bumps lean-toolchain to the latest stable release — the updater's default channel; release candidates are opt-in via release_channel — and moves plausible's pinned tag with it. The action opens a PR on an update/lean-{release} branch whether or not the build passes, so an incompatible release shows up as a failing PR to review rather than only an issue. The PR is opened with a GitHub App token so that it triggers CI.
plausible's pin changes from the short hash 6304553 to v4.31.0 — the same commit, since that hash is what the tag points at. Written as a version tag, the pin is managed by the updater's defaults; a future deliberate pin to a plain commit hash will be reported and left alone, pausing the automation until the pin is back on a tag.