Fix docs preview build failing on pnpm 11 release-age policy#1064
Merged
Conversation
The bump in 33b1e3b pulled in fumadocs 16.10.4, next 16.2.9, wrangler 4.102.0, and miniflare, all published within the pnpm 11 minimumReleaseAge window, which broke the docs preview build. Restore the prior aged versions; Renovate re-proposes them once they pass the cooldown.
Set Renovate minimumReleaseAge to 5 days and pnpm minimumReleaseAge to 3 days so day-old dependencies no longer enter the docs lockfile and fail the preview build.
Contributor
There was a problem hiding this comment.
Pull request overview
Fixes the docs preview CI build failing on pnpm 11 due to ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION by aligning pnpm’s release-age enforcement with Renovate’s dependency update cadence.
Changes:
- Configure pnpm (docs workspace) to enforce a 3-day
minimumReleaseAgeduring dependency resolution. - Configure Renovate to wait 5 days (
minimumReleaseAge) before proposing dependency updates, preventing “too-new” lockfile entries.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
docs/pnpm-workspace.yaml |
Adds minimumReleaseAge: 4320 (3 days) so pnpm won’t select packages younger than the policy window. |
.github/renovate.json |
Adds Renovate minimumReleaseAge: "5 days" to avoid generating lockfiles with packages that pnpm would reject. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Contributor
Documentation Preview
You're seeing this because the docs/samples were updated. |
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.
Describe the changes
Fixes the docs preview build, which was failing at
pnpm installwithERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION.minimumReleaseAge(1 day) by default and re-verifies the committed lockfile on every install. Renovate had no cooldown, so it bumped docs deps the moment they published, leaving the lockfile with packages younger than a day that CI then rejected (e.g.fumadocs 16.10.4,wrangler@4.102.0,miniflare).minimumReleaseAgecooldown to Renovate (.github/renovate.json) so it stops proposing day-old dependencies, including transitive ones (Renovate passes--beforeduring lockfile generation).minimumReleaseAgeto 3 days indocs/pnpm-workspace.yaml, keeping supply-chain protection at version-selection time while staying below the Renovate window.33b1e3be9dependency bump (fumadocs16.10.4 to 16.8.9,next/eslint-config-next16.2.9 to 16.2.6, and the lockfile back to its prior aged state) so the committed lockfile satisfies the cooldown with no CI override needed. Renovate will re-open these once they pass the 5-day window. The reverted versions are the ones the current docs content (typography, SEO) was built against, so there is no build regression.Checklist