Repository navigation
Lockfile maintenance - #60
Merged
Merged
Conversation
lockfile-maintenance
Bot
force-pushed
the
automation/lockfile-maintenance
branch
from
October 9, 2026 09:29
ee923ad to
8356d26
Compare
knu
approved these changes
Oct 9, 2026
Contributor
Merge Queue Status
This pull request spent 12 minutes 38 seconds in the queue, including 1 minute 43 seconds running CI. Required conditions to merge
|
This was referenced Oct 9, 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
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.
Update selected lockfiles with a minimum release age of
3 days.The package managers' native exceptions still apply. Validate updates with the repository's PR CI.
Version changes
Versions are grouped by package name. — means the package was not present.
Cargo.locklibc0.2.1890.2.190libc—0.2.189→0.2.190(1 release)Back to version changes · Compare · CHANGELOG.md · Releases
0.2.190Rebase
Check the box above or post a new PR comment with
/lockfile rebaseon its own line. Requires repository write access.Workflow requirements and manual fallback
Enable App-based rebase handling with
rebase: truein.github/lockfile-maintenance-auth.yml, or configure an Actions request handler as described below.For Actions-based handling, the workflow must subscribe to
pull_request_target: types: [edited]for the checkbox andissue_comment: types: [created]for comments, and configure the request-rebase job.If these handlers are not configured, open the maintenance workflow and select Run workflow on the branch used for maintenance. This requires
workflow_dispatch.