1. 01 Jul, 2026 2 commits
  2. 30 Jun, 2026 1 commit
  3. 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
  4. 10 Jun, 2026 1 commit
  5. 09 Jun, 2026 1 commit
  6. 03 Jun, 2026 2 commits
  7. 01 Jun, 2026 3 commits
  8. 07 May, 2026 7 commits
  9. 06 May, 2026 10 commits
  10. 27 Apr, 2026 6 commits
    • Benjamin Woodruff's avatar
      CI: Download and run self-contained datadog-ci instead of using pnpm dlx or npx (#92546) · ea3d78e2
      Benjamin Woodruff authored
      `pnpm dlx` isn't using a lockfile. Using the self-contained binary from
      GitHub and validate the checksum lets us effectively pin `datadog-ci`
      and all of its possible transitive dependencies.
      
      This is a follow-up for
      https://vercel.slack.com/archives/C0APPN2LC83/p1775073127894859
      
      (cherry picked from commit 631fae95)
      ea3d78e2
    • Zack Tanner's avatar
      [ci]: switch to GitHub runners (#93164) · f93e02f2
      Zack Tanner authored
      Switch CI from self-hosted runners to GitHub-hosted runners and fix the
      follow-up issues that showed up once the hosted jobs were exercised.
      
      - Move Linux workflows onto `ubuntu-latest-16-core-oss`, Windows
      workflows onto `windows-latest-8-core-oss`, and the native mac release
      lane onto `macos-15-intel`.
      - Update the reusable build workflow to work in hosted environments by
      relying on `runner.os` instead of label string matching, and by removing
      the hardcoded `/home/runner` `fnm` path.
      - Make Turbo/sccache configuration explicit for hosted runners:
        - unify on `vtest314-next-adapter-e2e-tests`
      - pass `TURBO_TOKEN` via workflow env/secrets instead of assuming
      runner-level env
      - switch Turbo cache mode to `local:rw,remote:rw` so jobs still have
      local cache behavior when remote cache is unavailable
      - Update the `sccache` action defaults/docs to use the hosted-runner
      secret setup (`TURBO_TOKEN`) instead of the old self-hosted token
      wiring.
      - Make Datadog reporting fail open so missing `DATA_DOG_API_KEY` does
      not block CI.
      - Fix the CLI reserved-port test so it asserts Next’s own `-p 1`
      validation instead of failing earlier on hosted Linux due to
      privileged-port binding.
      - Replace the live `musl.cc` dependency in `native-builder.Dockerfile`
      with musl sysroots imported from GHCR-hosted `rust-musl-cross` images,
      keeping the existing `/opt/*-cross` layout used by the Linux native
      build scripts.
      - Fix the macOS native build workaround s so it applies to all
      *-apple-darwin targets based on the Cargo target OS rather than the host
      architecture, which avoids napi-build injecting the unsupported -Wl
      linker arg when @next/swc is linked with rust-lld on hosted mac runners.
      
      Test Plan:
      - This PR's CI
      - This
      [build_and_deploy](https://github.com/vercel/next.js/actions/runs/24865715983/job/72801225722)
      job running on every arch
      
      (cherry picked from commit 70defda2)
      f93e02f2
    • Zack Tanner's avatar
      [ci]: trigger signed release commit via API (#93285) · 137d7645
      Zack Tanner authored
      Stacked on https://github.com/vercel/next.js/pull/93245
      
      Commit signing is required for anything that lands on `canary`. Our
      previous workflow of using a PAT to push a commit no longer works, since
      that would have been an unsigned commit.
      
      In #93245 we switched to an app token for release workflow steps. This
      continues by:
      
      - Telling Lerna to bump packages but not commit
      - Creating a signed commit with the staged changes via GitHub's API
      - Then running the publish flow
      
      Test Plan:
      Dry run
      [here](https://github.com/vercel/next.js/actions/runs/25001287978/job/73211826479)
      Commit
      [here](https://github.com/vercel/next.js/commit/3a8456a62b56615e2f8c1d1e6e7b4e14ce89e078)
      
      (cherry picked from commit 012fd7df)
      137d7645
    • Zack Tanner's avatar
      [ci]: app-based release workflow (#93245) · 27b8295b
      Zack Tanner authored
      Moves all release workflows off of a GH PAT and uses an app with a
      short-lived token instead.
      
      Test Plan:
      Dry run
      [here](https://github.com/vercel/next.js/actions/runs/24934593874).
      
      However, this workflow is blocked until we figure out commit signing for
      the bot app. Some options:
      - The bot account generates a signing key and we use it in CI (not
      great, bypasses the app)
      - The org bypasses signature verification for the bot user (also not
      great, requires an exemption rule)
      - We need to rework the commit step so Lerna does not do the push, and
      instead trigger it via the app + GH API. This seems like the best
      option, will be added in a follow-up PR.
      
      Note: `create-release-branch` workflow is broken in its current form, as
      we will not be restoring administrator privileges to adjust environment
      settings. This will become a manual step in the future.
      
      (cherry picked from commit e69de2ff)
      27b8295b
    • Zack Tanner's avatar
      [ci]: add environment to publishRelease flow (#93093) · ea1e8c3b
      Zack Tanner authored
      Moves the `environment` into `publishRelease` rather than
      `trigger_release` since the actual action we want to create environment
      rules for is the publish step.
      
      (cherry picked from commit 2b846de4)
      ea1e8c3b
    • Zack Tanner's avatar
      [ci]: remove publish token in favor of OIDC (#93065) · c01faddb
      Zack Tanner authored
      Switches from a long-lived token to trusted publishing OIDC flow. This requires a bump to Node (for feature support). Otherwise just dropping unnecessary envs.
      
      (cherry picked from commit 129896c2)
      c01faddb
  11. 22 Apr, 2026 1 commit
  12. 21 Apr, 2026 3 commits
  13. 08 Apr, 2026 1 commit