Repository navigation
fix: take our own releases past Dependabot's three-day wait - #20
Merged
Merged
Conversation
Dependabot holds new versions back three days and runs pnpm with that minimum release age, which refuses any locked version younger than it, so a weekly npm run within three days of one of our releases failed. Those are left out of the age in pnpm-workspace.yaml and in Dependabot's cooldown; other packages keep it. Closes #19
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
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.
Closes #19.
Dependabot holds new versions back three days and runs pnpm with
--config.minimum-release-age=4320, and pnpm then refuses every locked version younger than that. This site pins@missing-elementsreleases as they come out, so the next weekly npm run, due about 2026-11-12, would fail on h5p-author 0.6.0, locked 2026-11-09. The org site's daily job already does (missing-elements/missing-elements.github.io#9, fixed the same way in #10).pnpm-workspace.yaml(new, settings only):minimumReleaseAgeExclude: ["@missing-elements/*"]..github/dependabot.yml:cooldownkeeps the three days for every other package and excludes ours, so a release of ours gets its PR at the next weekly run rather than three days later.Checked locally with Dependabot's own command,
pnpm update @playwright/test --lockfile-only --config.minimum-release-age=…. Without the file it fails on h5p-author 0.6.0; with it, it passes, at the full three days too.pnpm install --frozen-lockfileis unchanged.Summary by cubic
Dependabot's three-day wait on new versions made pnpm refuse
@missing-elementspackages locked within the last three days, so weekly npm runs could fail. The newpnpm-workspace.yamlexcludes those packages from pnpm's minimum-release-age check, and Dependabot's cooldown now excludes them too; every other package keeps the three-day wait.Written for commit 439f58b. Summary will update on new commits.