Repository navigation
Conversation
This reverts commit 9a6a69b to keep the rc.2 release on the pnpm 11 toolchain the rc.1 publish ran on. The first CI run of the release branch under pnpm 12 lost two of the four "Test packages" shards to the task runner, not to a test: ✗ Failed to forward task process output: Resource temporarily unavailable (os error 11) vp run: 0/25 cache hit (0%), 4 failed. Every vitest run in those jobs passed. A re-run went green, so the failure is intermittent, and it only showed up on a cold task cache where every package rebuilds. The Deployment job builds every package from a clean cache before `pnpm -r publish`, so the same failure there would leave the release tagged on GitHub but unpublished on npm. Re-land the pnpm 12 upgrade after rc.2 ships, once the vp output forwarding failure under pnpm 12 is understood. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JZ5RTqfnRMiiASH1T7tWVj
✅ Deploy Preview for vjs-registry canceled.
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
✅ Deploy Preview for vjs10-site ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
@videojs/cdn
@videojs/core
@videojs/element
@videojs/html
@videojs/media
@videojs/react
@videojs/spf
@videojs/store
@videojs/utils
@videojs/cloudflare-video
@videojs/dash-video
@videojs/hlsjs-video
@videojs/mux-audio
@videojs/mux-video
@videojs/native-hls-video
@videojs/shaka-video
@videojs/spotify-audio
@videojs/tiktok-video
@videojs/twitch-video
@videojs/vimeo-video
@videojs/wistia-video
@videojs/youtube-video
@videojs/google-cast
@videojs/mux-data
commit: |
📦 Bundle Size Report🎨 @videojs/html — no changesPresets (7)
Media (18)
Players (5)
Skins (29)
UI Components (62)
⚛️ @videojs/react — no changesPresets (7)
Media (22)
Extensions (2)
Players (5)
Skins (18)
UI Components (39)
🧩 @videojs/core — no changesEntries (76)
🏷️ @videojs/element — no changesEntries (2)
📦 @videojs/store — no changesEntries (3)
🔧 @videojs/utils — no changesEntries (13)
📦 @videojs/cdn — no changes📦 @videojs/cloudflare-video — no changes📦 @videojs/dash-video — no changes📦 @videojs/google-cast — no changes📦 @videojs/hlsjs-video — no changes📦 @videojs/media — no changesEntries (3)
📦 @videojs/mux — no changes📦 @videojs/mux-audio — no changesEntries (2)
📦 @videojs/mux-data — no changes📦 @videojs/mux-video — no changesEntries (2)
📦 @videojs/native-hls-video — no changes📦 @videojs/shaka-video — no changes📦 @videojs/spf — no changesEntries (7)
📦 @videojs/spotify-audio — no changes📦 @videojs/tiktok-video — no changes📦 @videojs/twitch-video — no changes📦 @videojs/vimeo-video — no changes📦 @videojs/wistia-video — no changesEntries (2)
📦 @videojs/youtube-video — no changesℹ️ How to interpretEach entry is independently bundled, minified, and brotli-compressed. Initial size includes its static import graph; lazy dynamic chunks are reported separately. Entries are not additive because their dependency graphs overlap. Preset rows represent realistic combined bundles. Changes of 300 B or less across initial, lazy, and total size are collapsed, not discarded. Run |
|
Closing: this revert does not help. Its own CI failed the same two shards the same way under pnpm 11.17.0 (Test packages (2/4)): So the trigger is a cold Vite task cache (every package rebuilds and the runner forwards the full build output), not the pnpm major. pnpm 12 stays. Generated by Claude Code |
Why
Optional safety net for the rc.2 release. Reverts #2695 so the release publishes on the same pnpm 11 toolchain rc.1 shipped on. Re-land #2695 after rc.2 is out.
The first CI run of the release branch (#2670, commit 03c03c2) under pnpm 12 lost two of four
Test packagesshards to the task runner rather than to a test:Every vitest run in those jobs reported all tests passed. Failing jobs: Test packages (2/4), Test packages (4/4).
A re-run of the failed jobs went green, but it ran with a warm task cache (
20/29 cache hit), so it did not reproduce the conditions of the failure: a cold cache where every package rebuilds and the runner forwards the full build output. The Deployment job runspnpm cleanand builds every package beforepnpm -r publish, which is exactly that cold path. If the build step dies the same way there, release-please has already tagged and created the GitHub releases and nothing reaches npm.What
Plain
git revertof 9a6a69b. RestorespackageManager: pnpm@11.17.0,pnpm/action-setup@v4in the workflows, and the pnpm 11 lockfile entries.Not a diagnosis of pnpm 12
Whether pnpm 12 causes the EAGAIN or only exposes it is not established. A quick local check did not show pnpm 12 handing children a non-blocking stdout. This PR only removes the variable from the release.
🤖 Generated with Claude Code
https://claude.ai/code/session_01JZ5RTqfnRMiiASH1T7tWVj
Generated by Claude Code