Repository navigation
ci: re-run Dependabot CI once lockfile packages pass the release age - #248
Merged
Merged
Conversation
sadjow
force-pushed
the
ci/retry-release-age-failures
branch
from
October 29, 2026 14:05
0379d1d to
032ae29
Compare
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.
Reviewer card
minimumReleaseAge(one day by default in pnpm 11).trustLockfile, nominimumReleaseAgeExcludeentries, and no change to the auto-merge workflow.ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION), skipped chore(deps): update Nuxt, devtools, Vite, and node-forge to patched releases #246's passing run, and the log check rejected run 38804722699, which failed for another reason.actionlint(with shellcheck) and Prettier pass.actions: write). Deleting the file removes it.workflow_dispatch.Problem
Dependabot skips its cooldown for security updates by design, so a security PR can resolve transitive packages published minutes earlier.
pnpm install --frozen-lockfilere-verifies every lockfile entry againstminimumReleaseAge, so every CI job fails even though the change is sound. Auto-merge then waits on checks that never re-run, and the PR sits open. That happened to #245. Upstream, Dependabot does not writeminimumReleaseAgeExcludefor these updates yet (dependabot/dependabot-core#13854).Change
A scheduled workflow looks at each open Dependabot PR's latest CI run. When that run failed on the release-age check and finished more than a day ago, it re-runs the failed jobs. Because the lockfile is unchanged and its packages are now old enough, the re-run passes and the existing auto-merge completes. Failures for any other reason are left for review.