1. 03 Mar, 2026 13 commits
    • nextjs-bot's avatar
      v16.2.0-canary.73 · 82db9449
      nextjs-bot authored
      82db9449
    • Tim Neutkens's avatar
      Conditionally load uncommon paths (#90514) · 18e07cf4
      Tim Neutkens authored
      ## What?
      
      No changes in functionality. Just skips requiring modules that are not
      used in the common hot path of builds.
      
      ---------
      Co-authored-by: 's avatarTobias Koppers <tobias.koppers@googlemail.com>
      18e07cf4
    • Jan Nicklas's avatar
      exempt data URL CSS from Pages Router global CSS restriction (#89901) · 5fa40c80
      Jan Nicklas authored
      ### What?
      
      Skip the Pages Router global CSS restriction for `data:` URL imports
      (similar to app router and mixed app/pages router)
      
      ### Why?
      
      `data:text/css` should work the same no matter if pages router, app
      router or mixed router usage
      
      ### How?
      
      the validation in `crates/next-api/src/module_graph.rs` already had a
      carve-out for `node_modules`. This adds the same for data URL modules.
      
      fixes #89900
      
      - [x] Related issues linked using `fixes #89900`
      - [x] Tests added
      
      ---------
      Co-authored-by: 's avatarTim Neutkens <tim@timneutkens.nl>
      5fa40c80
    • Tobias Koppers's avatar
      pr-status: add --wait flag and background execution for /pr-status command (#90687) · cfd5d5db
      Tobias Koppers authored
      ## Summary
      
      - Add a `--wait` flag to `scripts/pr-status.js` that writes a partial
      report with currently available CI results, then blocks on `gh run
      watch` until CI completes, and re-runs the full analysis to produce the
      final report
      - Refactor `main()` into a reusable `runAnalysis()` function so it can
      be called twice (partial + final)
      - Update the `/pr-status` command to run the script with `--wait` in the
      background, present the partial report immediately while CI is still
      running, then poll for completion with 5-minute timeouts
      
      ### How it works
      
      1. `/pr-status` launches `node scripts/pr-status.js --wait` in the
      background (1-minute Bash timeout)
      2. The script writes the initial report (with whatever jobs have
      completed so far) and prints `Output written to ...`
      3. The command polls for that message using `TaskOutput` with 20-second
      timeouts, then reads `index.md` and analyzes the partial results
      4. Meanwhile, the script blocks on `gh run watch` until CI finishes,
      then re-runs the full analysis
      5. After presenting the partial analysis, the command polls for the
      background script to complete using `TaskOutput` with 5-minute timeouts
      (repeating if needed)
      6. When it finishes, the command re-reads the final report and analyzes
      any newly failed jobs
      
      ### Files changed
      
      - `scripts/pr-status.js` — Extracted `runAnalysis()` from `main()`,
      added `--wait` flag with `gh run watch` blocking and re-analysis
      - `.claude/commands/pr-status.md` — Updated workflow to use `--wait`
      with background execution, poll for readiness (20s timeouts), and poll
      for final results (5-min timeouts)
      
      ## Test plan
      
      - [ ] Run `node scripts/pr-status.js <completed-pr-number>` (no
      `--wait`) — should behave identically to before
      - [ ] Run `node scripts/pr-status.js <completed-pr-number> --wait` —
      should produce report and exit immediately (no waiting needed since CI
      is done)
      - [ ] Run `node scripts/pr-status.js --wait` on a branch with
      in-progress CI — should write partial report, block on `gh run watch`,
      then write final report
      - [ ] Run `/pr-status` command — should show partial results, then
      update with final results after CI completes
      
      ---------
      Co-authored-by: 's avatarClaude <noreply@anthropic.com>
      cfd5d5db
    • Luke Sandberg's avatar
      Add support for multi-valued tables (#89728) · 11823f84
      Luke Sandberg authored
      ## What
      
      Add support for multi-valued tables in `turbo-persistence`.
      
      A multi-valued table allows multiple distinct values to be associated
      with a single key. Each family is independently configured as
      `SingleValue` (existing behavior) or `MultiValue` via the new
      `FamilyKind` enum.
      
      ## Why
      
      This will support the `TaskCache` table (implemented in #88904), where
      keys will change to be _hashes_ instead of full `TaskType` values. This
      greatly decreases DB size and speeds up queries due to smaller key
      sizes, at the cost of hash collisions requiring multiple values per key.
      
      ## How
      
      ### API
      
      - New `FamilyKind` enum (`SingleValue` / `MultiValue`) and per-family
      `FamilyConfig` in `DbConfig`
      - `get()` for single-valued families (panics if called on multi-valued)
      - `get_multiple()` for multi-valued families, returns
      `SmallVec<[ArcBytes; 1]>` — stack-allocated for the common 0–1 result
      case, heap-scales when needed
      - `put()` and `delete()` are unchanged — the family kind controls
      dedup/compaction behavior
      
      ### Write path & compaction
      
      - **Single-valued** (unchanged): last-write-wins per key
      - **Multi-valued**: all values are maintained, deletions 'shadow' old
      values.
      - Deletion inserts a tombstone that shadows all older values for that
      key across SST layers. Values written *after* the tombstone in the same
      batch are retained.
      - To avoid extra buffering logic the `MergeIter` semantics were changed
      so it produces 'newest' entries first
      * for SingleValues families this is no different since we only keep one
      value
      * for MultiValued families this makes dealing with tombstones trivial,
      but does mean compaction will reverse the order of the set. For this
      reason we make no guarantees about ordering.
      
      ### Read path
      
      - Controlled by a `FIND_ALL` const generic on the internal lookup
      methods
      - **Single-valued** (`FIND_ALL=false`): binary search, return _last_
      match, stop
      * This fixes a bug where we might return Deleted when there is a value
      in the SST depending on what the search algorithm found first
      - **Multi-valued** (`FIND_ALL=true`): scan all matching entries in the
      SST block, then continue to older SSTs. If a tombstone is found, stop
      searching older layers.
      
      ---------
      Co-authored-by: 's avatarTobias Koppers <tobias.koppers@googlemail.com>
      11823f84
    • Joseph's avatar
      Create next app CLI docs (#90788) · 872c01b5
      Joseph authored
      <!-- Thanks for opening a PR! Your contribution is much appreciated.
      To make sure your PR is handled as smoothly as possible we request that
      you follow the checklist sections below.
      Choose the right checklist for the change(s) that you're making:
      
      ## For Contributors
      
      ### Improving Documentation
      
      - Run `pnpm prettier-fix` to fix formatting issues before opening the
      PR.
      - Read the Docs Contribution Guide to ensure your contribution follows
      the docs guidelines:
      https://nextjs.org/docs/community/contribution-guide
      
      ### Fixing a bug
      
      - Related issues linked using `fixes #number`
      - Tests added. See:
      https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
      - Errors have a helpful link attached, see
      https://github.com/vercel/next.js/blob/canary/contributing.md
      
      ### Adding a feature
      
      - Implements an existing feature request or RFC. Make sure the feature
      request has been accepted for implementation before opening a PR. (A
      discussion must be opened, see
      https://github.com/vercel/next.js/discussions/new?category=ideas)
      - Related issues/discussions are linked using `fixes #number`
      - e2e tests added
      (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
      - Documentation added
      - Telemetry added. In case of a feature if it's used or not.
      - Errors have a helpful link attached, see
      https://github.com/vercel/next.js/blob/canary/contributing.md
      
      
      ## For Maintainers
      
      - Minimal description (aim for explaining to someone not on the team to
      understand the PR)
      - When linking to a Slack thread, you might want to share details of the
      conclusion
      - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
      - Add review comments if necessary to explain to the reviewer the logic
      behind a change
      
      ### What?
      Updated `installation.mdx` and `create-next-app.mdx` documentation.
      
      ### Why?
      To accurately reflect the `create-next-app` CLI's behavior regarding
      `AGENTS.md` and `CLAUDE.md` file generation, and to update the displayed
      default configuration.
      
      ### How?
      - **`docs/01-app/01-getting-started/01-installation.mdx`**:
      - Updated `--yes` flag description to mention `AGENTS.md` and
      `CLAUDE.md` inclusion.
      - Corrected the recommended defaults prompt to replace "Turbopack" with
      "AGENTS.md".
          - Added the `AGENTS.md` prompt to the customize settings section.
      - **`docs/01-app/03-api-reference/06-cli/create-next-app.mdx`**:
          - Added `--agents-md` flag to the options table.
          - Updated recommended defaults and customize settings prompts.
      
      Closes NEXT-
      Fixes #
      
      -->
      
      ---
      [Slack
      Thread](https://vercel.slack.com/archives/C07BS1WEYAZ/p1772483393984349?thread_ts=1772483393.984349&cid=C07BS1WEYAZ)
      
      <p><a
      href="https://cursor.com/agents/bc-2f6bce63-8c1b-544a-9a10-cb65f56b213d"><picture><source
      media="(prefers-color-scheme: dark)"
      srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source
      media="(prefers-color-scheme: light)"
      srcset="https://cursor.com/assets/images/open-in-web-light.png"><img
      alt="Open in Web" width="114" height="28"
      src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a>&nbsp;<a
      href="https://cursor.com/background-agent?bcId=bc-2f6bce63-8c1b-544a-9a10-cb65f56b213d"><picture><source
      media="(prefers-color-scheme: dark)"
      srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source
      media="(prefers-color-scheme: light)"
      srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img
      alt="Open in Cursor" width="131" height="28"
      src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a>&nbsp;</p>
      
      ---------
      Co-authored-by: 's avatarCursor Agent <cursoragent@cursor.com>
      Co-authored-by: 's avatarJoseph <icyJoseph@users.noreply.github.com>
      872c01b5
    • Tobias Koppers's avatar
      Update Rust dependencies for turbo-persistence and turbo-tasks-backend (#90774) · 420b72b6
      Tobias Koppers authored
      ### What?
      
      Updates outdated Rust dependencies used by `turbo-persistence` and
      `turbo-tasks-backend` crates.
      
      ### Why?
      
      Keep dependencies current to benefit from bug fixes, performance
      improvements, and security patches.
      
      ### How?
      
      Each dependency was updated in a separate commit. All crates were
      verified to compile and tests pass.
      
      **Direct dependency updates:**
      - `lzzzz` 1.1.0 → 2.0.0 (moved to workspace dependency, used by both
      crates)
      - `arc-swap` 1.7.1 → 1.8.2 (turbo-tasks-backend)
      
      **Workspace dependency updates:**
      - `bitfield` 0.18 → 0.19
      - `either` 1.9 → 1.15
      - `indexmap` 2.7 → 2.13
      - `once_cell` 1.17 → 1.21
      - `rand` 0.9 → 0.10 (required API migration: `Rng`/`RngCore` → `RngExt`)
      - `ringmap` 0.1 → 0.2
      
      **Skipped:**
      - `hashbrown` 0.14 → 0.16: The `raw` module was removed in 0.15 and
      replaced with `HashTable` API. The codebase uses `RawTable`, `Bucket`,
      `InsertSlot` extensively, requiring a non-trivial migration.
      420b72b6
    • Niklas Mischkulnig's avatar
      Stub adapterPath with experimental.runtimeServerDeploymentId (#90790) · c3165ca5
      Niklas Mischkulnig authored
      `required-server-files.json` contains the `adapterPath` which might be nondeterministic across builds depending on where the adapter was installed.
      c3165ca5
    • Luke Sandberg's avatar
      [turbopack] Don't schedule idle snapshots when we are in a short session (#90804) · 8b70c610
      Luke Sandberg authored
      In a few `next build` commands i saw multiple snapshots due to this.  Idle callbacks were firing near the end of the build.
      
      ```
        Creating an optimized production build ...
      WARNING: The git repository is dirty, but File System Cache is still enabled. Manual removal of the filesystem cache database might be required.
      ✓ Finished writing to filesystem cache because: idle timeout in 6.1s
      ✓ Compiled successfully in 69s
      ✓ Collecting page data using 13 workers in 85ms
        Build ran with "compile" mode, to finalize the build run either "generate" or "generate-env" mode as well
      ✓ Finalizing page optimization in 32ms
      Route (app)
      ...ommitted route table...
      ✓ Finished writing to filesystem cache because: stop in 3.5s
      ```
      
      This is a bit wasteful since it is more efficient to write everything in a single batch at the end.
      
      The solution is just to not schedule snapshotting operations in 'short sessions' (aka `next build`)
      8b70c610
    • Tobias Koppers's avatar
      pr-status: add reply-thread and resolve-thread subcommands (#90773) · b7c11377
      Tobias Koppers authored
      ### What?
      
      Adds two new subcommands to `scripts/pr-status.js`:
      - `reply-thread <threadNodeId> <body>` — posts a reply to a PR review
      thread
      - `resolve-thread <threadNodeId>` — marks a review thread as resolved
      
      Each generated `thread-N.md` file now includes a `## Commands` section
      at the bottom with ready-to-use commands pre-populated with the correct
      GraphQL node IDs. The resolve command is only shown for threads that are
      still open.
      
      Also updates the pr-status-triage skill to remind agents to reply to
      review threads with a description of actions taken before resolving
      them.
      
      ### Why?
      
      When an agent addresses review feedback, it should close the loop by
      replying to the thread (describing what was done) and resolving it.
      Previously there was no way to do this from the pr-status workflow — the
      agent would need to manually construct `gh api graphql` calls.
      
      ### How?
      
      - Fetches GraphQL node IDs for review threads (added `id` to the
      thread-level query)
      - Uses `execFileSync` with argument arrays (not shell strings) to safely
      pass the reply body to `gh api graphql` without shell escaping issues
      - GraphQL mutations used: `addPullRequestReviewThreadReply` and
      `resolveReviewThread`
      - Subcommand dispatch at the top of `main()` checks `process.argv[2]`
      against known subcommand names before falling through to the existing
      PR-number behavior
      b7c11377
    • Tobias Koppers's avatar
      turbo-persistence: StreamingSstWriter performance and readability improvements (#90692) · 5102fd07
      Tobias Koppers authored
      ## Summary
      
      Performance and readability improvements to `StreamingSstWriter` in turbo-persistence, based on a performance audit of the streaming SST file builder.
      
      ### Pre-allocate Vec fields (33eb3e8f)
      - Pre-allocate `compress_buffer`, `pending_small_value_block`, `key_buffer`, `block_offsets`, and `key_block_boundaries` with capacity estimates derived from `max_entry_count`
      - Eliminates ~10-15 reallocations during early writes (e.g. for 1M-entry compaction files, the pre-allocation is ~89 KB across all Vecs)
      
      ### Readability cleanup (3de7a45a)
      - Extract `KeyBlockAccumulator` struct from four loose `current_key_block_*` fields, with `should_flush`/`add`/`reset` methods
      - Add architectural diagram comment for `pending_keys` queue layout showing resolved vs. unresolved regions
      - Name magic constant `BLOCK_INDEX_CAPACITY_BUFFER` (was bare `16`)
      - Simplify `flush_remaining_key_blocks()` using local `KeyBlockAccumulator` and remove dead state resets after `close()`
      - Remove `try_flush_key_block()` — its logic is now split between `KeyBlockAccumulator::should_flush()` and inline flush calls, which is clearer
      - Deduplicate `TestEntry` constructors via shared `new()` helper
      
      ### Derive value block estimate from constants (580e5d4c)
      - Replace magic number `40` (entries per value block) with `MIN_SMALL_VALUE_BLOCK_SIZE / AVG_SMALL_VALUE_SIZE` (= 128)
      - Add `AVG_SMALL_VALUE_SIZE = 64` constant
      
      ## Test Plan
      - All 14 existing `static_sorted_file_builder` tests pass: `cargo test -p turbo-persistence --lib -- static_sorted_file_builder`
      - No behavioral changes — all changes are internal to the writer
      5102fd07
    • Zack Tanner's avatar
      enable server action RDC deploy test (#90796) · bbb72bf2
      Zack Tanner authored
      <!-- Thanks for opening a PR! Your contribution is much appreciated.
      To make sure your PR is handled as smoothly as possible we request that
      you follow the checklist sections below.
      Choose the right checklist for the change(s) that you're making:
      
      ## For Contributors
      
      ### Improving Documentation
      
      - Run `pnpm prettier-fix` to fix formatting issues before opening the
      PR.
      - Read the Docs Contribution Guide to ensure your contribution follows
      the docs guidelines:
      https://nextjs.org/docs/community/contribution-guide
      
      ### Fixing a bug
      
      - Related issues linked using `fixes #number`
      - Tests added. See:
      https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
      - Errors have a helpful link attached, see
      https://github.com/vercel/next.js/blob/canary/contributing.md
      
      ### Adding a feature
      
      - Implements an existing feature request or RFC. Make sure the feature
      request has been accepted for implementation before opening a PR. (A
      discussion must be opened, see
      https://github.com/vercel/next.js/discussions/new?category=ideas)
      - Related issues/discussions are linked using `fixes #number`
      - e2e tests added
      (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
      - Documentation added
      - Telemetry added. In case of a feature if it's used or not.
      - Errors have a helpful link attached, see
      https://github.com/vercel/next.js/blob/canary/contributing.md
      
      
      ## For Maintainers
      
      - Minimal description (aim for explaining to someone not on the team to
      understand the PR)
      - When linking to a Slack thread, you might want to share details of the
      conclusion
      - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
      - Add review comments if necessary to explain to the reviewer the logic
      behind a change
      
      ### What?
      
      ### Why?
      
      ### How?
      
      Closes NEXT-
      Fixes #
      
      -->
      bbb72bf2
    • Josh Story's avatar
      Add static error when `unstable_instant` is used without `cacheComponents` (#90793) · 410c6580
      Josh Story authored
      `unstable_instant` requires `cacheComponents` to function — without it,
      validation is entirely skipped and the config silently does nothing.
      This adds a compile-time error in the SWC transform that catches the
      misconfiguration early, matching the existing pattern used for segment
      configs like `revalidate` that are incompatible with `cacheComponents`
      (but inverted — `unstable_instant` requires it rather than being
      incompatible with it). The error points directly to the export in the
      user's source file.
      410c6580
  2. 02 Mar, 2026 16 commits
  3. 01 Mar, 2026 7 commits
    • nextjs-bot's avatar
      v16.2.0-canary.70 · 5e3af2ce
      nextjs-bot authored
      5e3af2ce
    • Andrew Clark's avatar
      instant(): fix cookie handling for fresh page loads (#90613) · a362fd27
      Andrew Clark authored
      Previously, instant() used page.evaluate() to set the cookie via
      document.cookie, which required a page to already be loaded. This meant
      the cookie wasn't present on the very first navigation.
      
      Switch to Playwright's browser context cookie API so the cookie is set
      before any page loads. If the page is already loaded, the base URL is
      inferred automatically. Otherwise, a new baseURL option allows setting
      the cookie before the first navigation.
      a362fd27
    • Andrew Clark's avatar
      experimental.prefetchInlining: bundle segment prefetches into a single response (#90555) · 9ce8d136
      Andrew Clark authored
      ## Background
      
      Next.js 16 introduced per-segment prefetching through the Client Segment
      Cache. Rather than fetching all data for a route in a single request,
      the client issues individual requests for each segment in the route
      tree. This design improves cache efficiency: shared layouts between
      sibling routes (e.g., /dashboard/settings and /dashboard/profile sharing
      a /dashboard layout) are fetched once and reused from the client cache,
      avoiding redundant data transfer.
      
      The trade-off is request volume. A route with N segments now produces N
      prefetch requests instead of one. Users upgrading from older versions
      notice significantly more network activity in their devtools, even
      though the total bytes transferred may be similar or lower due to
      deduplication.
      
      Per-segment fetching is still a reasonable default for many sites. These
      prefetch requests are served from cache, they're fast, and they run in
      parallel. The main scenario where the trade-off breaks down is
      deployment environments that charge per-request. But even setting aside
      cost, there is a theoretical performance threshold where very small
      segments are better off inlined — the per-request overhead (connection
      setup, headers, scheduling) exceeds the cost of transferring duplicate
      bytes. This is analogous to JS bundlers, which inline small modules
      rather than creating separate chunks, because the overhead of an
      additional script tag or dynamic import outweighs the bytes saved.
      
      ## What this change does
      
      This adds `experimental.prefetchInlining`, a boolean option in
      next.config.js. When enabled, the server bundles all segment data for a
      route into a single `/_inlined` response rather than serving each
      segment individually. The tree prefetch (`/_tree`), which provides route
      structure metadata, remains a separate request — but optimistic routing
      (#88965) eliminates that request entirely by predicting the route
      structure client-side. With both features enabled, prefetching is
      effectively one request per link.
      
      The fundamental trade-off is straightforward: inlining reduces request
      count at the cost of deduplication. Each inlined response includes its
      own copy of any shared layout data, so two sibling routes will each
      transfer the shared layout rather than sharing a single cached copy.
      This is the same trade-off that compilers and bundlers face when
      deciding whether to inline a function: inlining eliminates the overhead
      of indirection (here, extra HTTP requests) but increases total size when
      the same data appears in multiple call sites.
      
      ## Future direction
      
      The boolean flag is a stepping stone. The observation that there is a
      natural size threshold below which inlining is strictly better — where
      per-request overhead dominates the cost of any duplicate bytes — points
      toward a size-based heuristic, analogous to how compilers choose an
      inlining threshold. Small segments would be inlined automatically;
      segments exceeding a byte threshold would be "outlined" into separate
      requests where deduplication can take effect. For most applications,
      this would require no configuration. For applications with specific
      latency or bandwidth constraints, an option to adjust the threshold
      would let developers tune their position on the requests-vs-bytes curve.
      Adaptive heuristics based on network conditions are also possible,
      though further out.
      9ce8d136
    • Michal Piechowiak's avatar
      feat: provide nextVersion to modifyConfig adapter hook (#90735) · 4d2ac245
      Michal Piechowiak authored
      For providers that either don't manage or allow for custom build
      commands, checking Next.js version in their builders is not reliable.
      Especially for providers that already have existing support there needs
      to be very reliable way to only apply certain configuration adjustments
      for supported versions of Adapters API.
      
      So this adds `nextVersion` to `modifyConfig` to allow that. It also
      brings parity to this hook (`onBuildComplete` already does receive
      `nextVersion`.
      
      Corresponding adjustments for docs (just types update) prepared in
      https://github.com/vercel/next.js/compare/canary...pieh:next.js:docs/nextVersion-in-adapter-modifyConfig
      
      <!-- Thanks for opening a PR! Your contribution is much appreciated.
      To make sure your PR is handled as smoothly as possible we request that
      you follow the checklist sections below.
      Choose the right checklist for the change(s) that you're making:
      
      ## For Contributors
      
      ### Improving Documentation
      
      - Run `pnpm prettier-fix` to fix formatting issues before opening the
      PR.
      - Read the Docs Contribution Guide to ensure your contribution follows
      the docs guidelines:
      https://nextjs.org/docs/community/contribution-guide
      
      ### Fixing a bug
      
      - Related issues linked using `fixes #number`
      - Tests added. See:
      https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
      - Errors have a helpful link attached, see
      https://github.com/vercel/next.js/blob/canary/contributing.md
      
      ### Adding a feature
      
      - Implements an existing feature request or RFC. Make sure the feature
      request has been accepted for implementation before opening a PR. (A
      discussion must be opened, see
      https://github.com/vercel/next.js/discussions/new?category=ideas)
      - Related issues/discussions are linked using `fixes #number`
      - e2e tests added
      (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
      - Documentation added
      - Telemetry added. In case of a feature if it's used or not.
      - Errors have a helpful link attached, see
      https://github.com/vercel/next.js/blob/canary/contributing.md
      
      
      ## For Maintainers
      
      - Minimal description (aim for explaining to someone not on the team to
      understand the PR)
      - When linking to a Slack thread, you might want to share details of the
      conclusion
      - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
      - Add review comments if necessary to explain to the reviewer the logic
      behind a change
      
      ### What?
      
      ### Why?
      
      ### How?
      
      Closes NEXT-
      Fixes #
      
      -->
      4d2ac245
    • Sebastian "Sebbie" Silbermann's avatar
    • Jiwon Choi's avatar
      Use commit-based tarball URL in PR stats comment (#90709) · 4e6beadc
      Jiwon Choi authored
      The previous method of using the PR endpoint under the hood calls the
      GitHub API to get the commit SHA, which is a waste of resources, so just
      use the commit SHA directly in the tarball URL.
      4e6beadc
    • Sebastian "Sebbie" Silbermann's avatar
  4. 28 Feb, 2026 4 commits