Repository navigation
Take our own releases past Dependabot's three-day wait - #10
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. The site pins @missing-elements releases on the day they come out, so the daily npm job failed after every one. They are left out of the age in pnpm-workspace.yaml and in Dependabot's cooldown; other packages keep it. Closes #9
![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 #9.
The daily npm update job has failed since 2026-11-09. 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 on the day they come out, so the job failed after each one.pnpm-workspace.yaml(new, settings only):minimumReleaseAgeExclude: ["@missing-elements/*"], so pnpm's age check passes our own releases..github/dependabot.yml:cooldownkeeps the three days for every other package and excludes ours, so a release of ours gets its PR the same day.Checked locally with Dependabot's own command,
pnpm update @11ty/eleventy@3.1.8 --lockfile-only --config.minimum-release-age=720. Without the file it fails on h5p-author 0.6.0; with it, it passes. A 12-hour age is used because the three-day one still trips on third-party versions (below).pnpm install --frozen-lockfileis unchanged.Not fixed by this: the job stays red until about 2026-11-13. rolldown 1.2.18 and a few other third-party versions locked on 2026-11-10 are younger than three days, which only time settles.
Summary by cubic
Fixes #9. The daily npm update job has failed since 2026-11-09 because Dependabot holds new versions back three days and pnpm refuses locked versions younger than that, while this site pins
@missing-elementsreleases on release day. Excludes@missing-elements/*from the age check in pnpm and Dependabot so our releases get PRs the same day.minimumReleaseAgeExcludein newpnpm-workspace.yaml.cooldownin.github/dependabot.yml: three days for all other packages, none for ours.Not fixed by this: the job stays red until about 2026-11-13; third-party versions locked on 2026-11-10 are still under three days old.
Written for commit f6d006a. Summary will update on new commits.