Skip to content

chore(deps): exclude scheduler from the minimum release age - #3261

Merged
christianhg merged 1 commit into
mainfrom
exclude-scheduler-release-age
Sep 10, 2026
Merged

christianhg merged 1 commit into
mainfrom
exclude-scheduler-release-age

Conversation

@christianhg

@christianhg christianhg commented Sep 10, 2026

Copy link
Copy Markdown
Member

Renovate's react PRs arrive without a lockfile update and every CI job fails at pnpm install --frozen-lockfile (#3260). The workspace excludes react and react-dom from minimumReleaseAge, but not scheduler, which ships from the React monorepo in the same release: react-dom@19.3.0 requires a scheduler published the same day, so pnpm's lockfile update fails inside the 3-day age window and Renovate opens the PR with manifest edits only.

This PR adds scheduler to minimumReleaseAgeExclude. Verified by regenerating the lockfile with the react catalog entries at ^19.3.0: it fails with ERR_PNPM_NO_MATURE_MATCHING_VERSION without the exclusion and resolves with it. Current resolution is unchanged. After this merges, ticking the rebase checkbox on #3260 should produce a green lockfile-included update.


Note

Low Risk
pnpm workspace policy only; no runtime or application code changes.

Overview
Adds scheduler to minimumReleaseAgeExclude in pnpm-workspace.yaml, alongside the existing react / react-dom exclusions.

That closes a gap where a react-dom bump can pull a same-day scheduler release that is still inside the 3-day minimumReleaseAge window, causing pnpm install --frozen-lockfile / lockfile regeneration to fail with ERR_PNPM_NO_MATURE_MATCHING_VERSION on Renovate React updates.

Reviewed by Cursor Bugbot for commit cba4d7a. Bugbot is set up for automated code reviews on this repo. Configure here.

`react` and `react-dom` are on `minimumReleaseAgeExclude`, but
`react-dom` depends on `scheduler`, which ships from the React
monorepo in the same release. When Renovate bumped the react catalog
entries to ^19.3.0 (#3260), pnpm's lockfile update failed with
`ERR_PNPM_NO_MATURE_MATCHING_VERSION`: `react-dom@19.3.0` requires
`scheduler@^0.28.0`, whose only satisfying version was published the
same day, inside the 3-day age window. Renovate then opened the PR
with manifest edits but no lockfile, and every CI job failed at
`pnpm install --frozen-lockfile`.

Excluding `scheduler` lets a react bump resolve immediately, matching
the trust already extended to `react`, `react-dom`, and `react-is`.
Verified by regenerating the lockfile with the react catalog entries
at ^19.3.0: fails with the mature-version error without the exclusion,
resolves with it. Resolution of the current lockfile is unchanged.
@vercel

vercel Bot commented Sep 10, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
portable-text-example-basic Ready Ready Preview Sep 10, 2026 6:59am UTC
portable-text-playground Ready Ready Preview Sep 10, 2026 6:59am UTC

Request Review

@changeset-bot

changeset-bot Bot commented Sep 10, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: cba4d7a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions

github-actions Bot commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

Bundle Stats

✅ No significant changes.

All scenario measurements (7)

🗺️ @portabletext/editor / @portabletext/editor · @portabletext/editor / @portabletext/editor/behaviors · @portabletext/editor / @portabletext/editor/plugins · @portabletext/editor / @portabletext/editor/selectors · @portabletext/editor / @portabletext/editor/traversal · @portabletext/editor / @portabletext/editor/utils · @portabletext/markdown / @portabletext/markdown · Artifacts

Scenario Kind Bundle (raw / gzip) Gzip change Import time Import change
⚪ @portabletext/editor / @portabletext/editor export 1.09 MB / 254.3 KB None 69 ms +0 ms, +0.7%
⚪ @portabletext/editor / @portabletext/editor/behaviors export 4.0 KB / 1.4 KB None 2 ms +0 ms, +1.6%
⚪ @portabletext/editor / @portabletext/editor/plugins export 5.1 KB / 1.8 KB None 7 ms +0 ms, +3.9%
⚪ @portabletext/editor / @portabletext/editor/selectors export 94.7 KB / 21.7 KB None 8 ms -0 ms, -1.3%
⚪ @portabletext/editor / @portabletext/editor/traversal export 42.8 KB / 11.2 KB None 6 ms +0 ms, +3.0%
⚪ @portabletext/editor / @portabletext/editor/utils export 33.8 KB / 9.1 KB None 6 ms -0 ms, -1.0%
⚪ @portabletext/markdown / @portabletext/markdown export 313.4 KB / 90.9 KB None 41 ms -0 ms, -0.2%

Significant means at least 1.0 KB and 1% gzip, or at least 5 ms and 10% import time.

@christianhg
christianhg marked this pull request as ready for review September 10, 2026 07:00
@christianhg
christianhg merged commit 3220ebb into main Sep 10, 2026
20 checks passed
@christianhg
christianhg deleted the exclude-scheduler-release-age branch September 10, 2026 07:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant