This appears to be an npm registry publishing issue being handled by maintainers.
The issue describes a dependency version mismatch in React DOM canary releases, but maintainers indicate this is caused by npm registry publishing problems they're actively investigating. This requires coordination with npm support and internal release processes, making it unsuitable for external contributors to address.
React version: Canary
Link to code example: You can see it in the package.json, just search for that canary version in the published packages https://www.npmjs.com/package/react-dom/v/19.3.0-canary-10680271-20260126?activeTab=code https://www.npmjs.com/package/scheduler?activeTab=versions
Claim this issue to let others know you're working on it. You'll earn 10 points when you complete it!