[pull] canary from vercel:canary

.github/workflows/sync_backport_canary_release.yml

@@ -121,20 +121,14 @@ jobs:
     needs: evaluate
     if: ${{ needs.evaluate.outputs.should_dispatch == 'true' && ((github.event_name == 'workflow_dispatch' && inputs.dispatch) || (github.event_name == 'workflow_run' && vars.ENABLE_BACKPORT_CANARY_SYNC == 'true')) }}
     runs-on: ubuntu-latest
-    steps:
-      - name: Create GitHub App token
-        id: release-app-token
-        uses: actions/create-github-app-token@bcd2ba49218906704ab6c1aa796996da409d3eb1 # v3.2.0
-        with:
-          client-id: ${{ vars.RELEASE_GITHUB_APP_CLIENT_ID }}
-          private-key: ${{ secrets.RELEASE_GITHUB_APP_PRIVATE_KEY }}
-          owner: ${{ github.repository_owner }}
-          repositories: next.js
-          permission-actions: write
+    permissions:
+      actions: write
 
+    steps:
       - uses: actions/github-script@d746ffe35508b1917358783b479e04febd2b8f71 # v9.0.0
         with:
-          github-token: ${{ steps.release-app-token.outputs.token }}
+          # workflow_dispatch events created with GITHUB_TOKEN start workflow runs.
+          github-token: ${{ github.token }}
           script: |
             await github.request(
               "POST /repos/{owner}/{repo}/actions/workflows/{workflow_id}/dispatches",

turbopack/crates/turbo-persistence/src/write_batch.rs

@@ -633,7 +633,7 @@ const fn usize_from_u32(value: u32) -> usize {
     // This should always be true, as we assume at least a 32-bit width architecture for Turbopack.
     // Since this is a const expression, we expect it to be compiled away.
     const {
-        assert!(u32::BITS < usize::BITS);
+        assert!(u32::BITS <= usize::BITS);
     };
     value as usize
 }

turbopack/crates/turbopack-tracing/tests/unit.rs

@@ -102,11 +102,22 @@ static ALLOC: turbo_tasks_malloc::TurboMalloc = turbo_tasks_malloc::TurboMalloc;
 #[case::esm_export_wildcard("esm-export-wildcard")]
 #[case::esm_paths("esm-paths")]
 #[case::esm_paths_trailer("esm-paths-trailer")]
+// nft traces a package's legacy `main` in addition to the target its `exports` field
+// resolves to (unless nft's `exportsOnly` option is set), so its reference output lists
+// `index.js` next to `require-main.cjs`, while Turbopack only traces the file it actually
+// resolves to.
 // #[case::exports("exports")]
+// Two reasons: as for `exports` above, nft also traces the legacy resolution (here the
+// directory index `index.js`). On top of that, Turbopack resolves this fixture's `exports`
+// fallback array to nothing at all, because it stops at the invalid first target
+// (`"in:valid"`) instead of continuing with the next entry, so `require-main.cjs` is missed.
 // #[case::exports_fallback("exports-fallback")]
 #[case::exports_nomodule("exports-nomodule")]
-// #[case::exports_only("exports-only")]
-// #[case::exports_path("exports-path")]
+// `exports-only` is the same fixture as `exports`, but nft traces it with `exportsOnly:
+// true`, which matches Node's (and Turbopack's) semantics of ignoring `main` when an
+// `exports` field is present.
+#[case::exports_only("exports-only")]
+#[case::exports_path("exports-path")]
 #[case::exports_wildcard("exports-wildcard")]
 // #[case::ffmpeg_installer("ffmpeg-installer")]
 #[case::file_folder_slash("file-folder-slash")]