[ci] Bump lock-threads, stale and typos actions to current versions - #8339
Merged
Conversation
* dessant/lock-threads v5 -> v6, the only breaking change is the Node.js 24 requirement * actions/stale v10 -> v11, an ESM and dependency update with no input changes * crate-ci/typos v1.46.0 -> v1.49.0 typos v1.49.0 was run locally over the same file list the workflow checks and reports no new findings.
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
1 participant
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.
Follow-up to #8335 and #8336, covering the last three actions still on an older version.
dessant/lock-threadsv5v6actions/stalev10v11crate-ci/typosv1.46.0v1.49.0Why these are safe
lock-threadsv5 -> v6. The changelog lists exactly one breaking change:No inputs changed, so
github-token,pr-inactive-days,pr-commentandexclude-any-pr-labelsall still apply.stalev10 -> v11. An ESM migration plus abrace-expansionsecurity bump; no breaking changes and no input changes. The Node 24 jump already happened inv10, which this repo is on.typosv1.46.0 -> v1.49.0. Atyposbump can fail CI on its own, because new dictionary entries can flag words that used to pass. Ranv1.49.0locally over the exact file list the workflow checks:No new findings.
After this, every action in
.github/workflowsis on its current major.