1. 21 Jul, 2026 10 commits
  2. 16 Jul, 2026 1 commit
  3. 01 Jul, 2026 2 commits
  4. 30 Jun, 2026 1 commit
  5. 17 Jun, 2026 2 commits
    • Jiwon Choi's avatar
      [15.5.x][ci] Port sccache fallback from #91873/#92911/#93164/#94319 (#94848) · c8f9fcb5
      Jiwon Choi authored
      ### Why?
      
      Stacked replacement for #94844. This is the top PR in the `next-15-5`
      backport stack and is based on #94847.
      
      This was discovered while investigating the fork PR CI failure on
      #94829.
      
      Fork PRs to `next-15-5` do not receive `secrets.TURBO_TOKEN`, but the
      pinned `ijjk/rust-cache` action throws when `TURBO_TOKEN` is missing.
      Canary no longer uses that action for these Rust cache paths; it starts
      the local `sccache` action and only configures Vercel Artifacts when a
      token is available.
      
      This ports the fork-safe cache behavior from canary without taking the
      broader native-builder and workflow rewrites from the source PRs.
      
      Source PRs / ported parts:
      
      - #91873: add the local `.github/actions/sccache` action and move Rust
      workflows off `ijjk/rust-cache`.
      - #92911: install `cargo-binstall` and use the `vercel/sccache`
      cargo-binstall path.
      - #93164: keep the Vercel Artifacts token/team wiring used by canary.
      - #94319: remove the remaining `build_and_deploy.yml` `ijjk/rust-cache`
      step.
      
      ### How?
      
      - Add the canary `.github/actions/sccache` action and install
      `cargo-binstall` from `setup-rust`.
      - Replace the remaining `ijjk/rust-cache` usage in reusable Rust
      workflows with the local `sccache` action.
      - Remove the remaining `build_and_deploy.yml` rust-cache step so fork
      PRs do not load the token-requiring external action.
      
      <!-- NEXT_JS_LLM_PR -->
      c8f9fcb5
    • Jiwon Choi's avatar
      [backport] [test] Fix external rewrite target URL origin (#94829) · 019fcca5
      Jiwon Choi authored
      ### Why?
      
      Backports https://github.com/vercel/next.js/pull/86863 to `next-15-5` so
      the skip-trailing-slash-redirect fixture rewrites to the assigned custom
      domain instead of the protected deployment-specific URL.
      
      ### How?
      
      - Cherry-picked `551b32d8` with `-x`.
      - Updates `test/e2e/skip-trailing-slash-redirect/app/middleware.js` to
      use `https://middleware-external-rewrite-target.vercel.app`.
      
      ### Verification
      
      - `pnpm build` passed. (`pnpm build-all` is not available on
      `next-15-5`.)
      - Not run: `pnpm test-start
      test/e2e/skip-trailing-slash-redirect/index.test.ts` (stopped per
      follow-up request to just cherry-pick and open PR).
      - Not run: `pnpm test-start-turbo
      test/e2e/skip-trailing-slash-redirect/index.test.ts` (stopped per
      follow-up request to just cherry-pick and open PR).
      
      <!-- NEXT_JS_LLM_PR -->
      Co-authored-by: 's avatarHendrik Liebau <mail@hendrik-liebau.de>
      019fcca5
  6. 10 Jun, 2026 1 commit
  7. 09 Jun, 2026 1 commit
  8. 03 Jun, 2026 2 commits
  9. 01 Jun, 2026 3 commits
  10. 07 May, 2026 7 commits
  11. 06 May, 2026 10 commits