1. 23 Oct, 2026 2 commits
  2. 22 Oct, 2026 2 commits
    • Tobias Koppers's avatar
      [lts-active] Keep OpenTelemetry request traces together (#100349, #100294,… · 37d603bf
      Tobias Koppers authored
      [lts-active] Keep OpenTelemetry request traces together (#100349, #100294, #100324, #100350, #100552, #100583) (#100542)
      
      Backports the OpenTelemetry request-trace stack to
      `releases/lts/active`:
      
      - #100349 Start the request span before route module preparation
      - #100294 Keep middleware and render in one OpenTelemetry trace as
      siblings (re-lands #100136, whose LTS backport #100226 was reverted in
      #100269)
      - #100324 docs: note that instrumentation-time spans don't join request
      traces
      - #100350 Emit instrumentation lifecycle spans in the request that
      registered it
      - #100552 Preserve deferred middleware instrumentation spans when the
      adapter throws
      - #100583 test: add non-adapter deploy snapshots to
      otel-middleware-trace. Without it, `otel-middleware-trace` fails the
      release deploy tests that deploy with `NEXT_ENABLE_ADAPTER=0`, as on
      v16.5.0-canary.23.
      
      The six canary merge commits are cherry-picked in order with `-x`, and
      all applied cleanly. The patch content is identical to canary's; only
      blob IDs and line offsets differ.
      
      ## Verification
      
      - `test/e2e/opentelemetry/instrumentation/`: `test-start-turbo` (122
      passed) and `test-dev-turbo` (67 passed). The #100552 regression test
      fails without its `middleware.ts` change.
      - `test/e2e/app-dir/otel-middleware-trace`: `test-start-turbo`,
      `test-dev-turbo` and `test-start-webpack` (30 passed each, inline
      snapshots unchanged). The #100583 commit leaves the test file
      byte-identical to canary's.
      - Unit tests for `instrumentation-globals`, `tracer` and
      `forward-trace-context` (40 passed), plus `pnpm --filter=next types`
      - Built with `CI=true pnpm build-all` against the published `@next/swc`
      16.4.2 binary. The backport touches no Rust.
      - PR CI deploys only through the adapter, so the non-adapter snapshots
      from #100583 are confirmed by the next release deploy run.
      
      <!-- NEXT_JS_LLM -->
      
      
      <!-- fleet ce0ecb23-b14c-4679-92a9-e676130f618e -->
      
      ---------
      Co-authored-by: 's avatarvercel-fleet-prod[bot] <318278635+vercel-fleet-prod[bot]@users.noreply.github.com>
      Co-authored-by: 's avatarLuke Sandberg <210140+lukesandberg@users.noreply.github.com>
      37d603bf
    • Sebastian "Sebbie" Silbermann's avatar
      [lts-active][cd] Move release un-draft to a follow-up job in bot-autonomous (#100572) · cf9d27d9
      Sebastian "Sebbie" Silbermann authored
      Backports #100571
      
      We currently only undraft prereleases so this isn't affecting anything
      on this branch. Mostly for parity so that any future undrafting "just"
      works.
      
      ---------
      Co-authored-by: 's avatarClaude Code <noreply@anthropic.com>
      cf9d27d9
  3. 21 Oct, 2026 1 commit
  4. 20 Oct, 2026 3 commits
  5. 19 Oct, 2026 1 commit
  6. 15 Oct, 2026 6 commits
  7. 14 Oct, 2026 9 commits
    • Luke Sandberg's avatar
      [lts-active] Turbopack: Ignore realpath errors during module resolution,… · 8ad85240
      Luke Sandberg authored
      [lts-active] Turbopack: Ignore realpath errors during module resolution, matching node's behavior (#100217)
      
      Backports [Turbopack: Ignore realpath errors during module resolution,
      matching node's behavior
      (#99951)](https://github.com/vercel/next.js/pull/99951) to
      `releases/lts/active`. The cherry-pick applied cleanly.
      
      ## Verification
      
      - `cargo test -p turbopack-core --lib resolve::`, using this branch's
      pinned toolchain: 65/65 tests passed. On macOS this needs a symlink-free
      `TMPDIR`, because the default temp dir is under `/var` → `/private/var`.
      That affects every resolve test on this branch, not just this change.
      - `cargo check --release -p turbopack-core`: clean. Removing `bail!`
      leaves no unused import.
      
      <!-- NEXT_JS_LLM -->
      Co-authored-by: 's avatarBenjamin Woodruff ‮ <benjamin.woodruff@vercel.com>
      8ad85240
    • Luke Sandberg's avatar
      [lts-active] [turbopack] Fix two GC paths that leave half-torn-down dependency edges (#100209) · 29d030e8
      Luke Sandberg authored
      Backports [[turbopack] Fix two GC paths that leave half-torn-down
      dependency edges (#99902)](https://github.com/vercel/next.js/pull/99902)
      to `releases/lts/active`.
      
      Builds on #100002, which brought over the snapshot rework (#99644,
      #99649) that this fix depends on.
      
      ## Conflict resolution
      
      `storage.rs` conflicted because #99747 (capture snapshot pending bits
      under exclusion) is not on this branch. The fix itself applies
      unchanged. The resolution only adjusts the surrounding code:
      
      - The snapshot scan takes #99902's loop as-is. The shard guard is
      already a write lock, so switching from `iter()` to `iter_mut()` is
      safe.
      - Added only the `is_deleted_new_task` helper.
      `debug_assert_persistable` does not exist on this branch.
      - Ported the three new storage tests to the `storage.take_snapshot(..)`
      method form. Dropped one `any_snapshot_pending()` assert, because that
      helper only exists after #99747.
      
      
      <!-- NEXT_JS_LLM -->
      29d030e8
    • Luke Sandberg's avatar
      [lts-active] fix(next-code-frame): snap visible window to char boundaries (#100212) · 3e50b822
      Luke Sandberg authored
      Backports [fix(next-code-frame): snap visible window to char boundaries
      (#92646)](https://github.com/vercel/next.js/pull/92646) to
      `releases/lts/active`. The cherry-pick applied cleanly.
      
      ## Verification
      
      - `cargo test -p next-code-frame`, using this branch's pinned toolchain:
      53/53 tests passed.
      
      <!-- NEXT_JS_LLM -->
      Co-authored-by: 's avatarmugi-uno <mugi.uno@gmail.com>
      Co-authored-by: 's avatarNiklas Mischkulnig <4586894+mischnic@users.noreply.github.com>
      3e50b822
    • Tobias Koppers's avatar
      [lts-active] Turbopack: backport Pages Router dev module graph chaining (#98823,… · 9458fb99
      Tobias Koppers authored
      [lts-active] Turbopack: backport Pages Router dev module graph chaining (#98823, #99910, #100091) (#100008)
      
      ## Summary
      
      Backports these canary commits to `releases/lts/active`:
      
      | PR | Commit | Change |
      | --- | --- | --- |
      | #98823 | `6dd4b27b` | Chain the Pages
      Router dev client module graphs to fix `_app` availability (#99789). |
      | #99910 | `1e1f9e69` | Add Pages Router
      availability coverage and restore the import-order assertion. |
      | #100091 | `5eec1d9d` | Fix `_app`
      `next/dynamic` preload 404s introduced by #98823, and preload those
      imports in production too. |
      
      The third commit must ship with #98823: chaining the page and `_app`
      graphs made pages preload `_app`'s dynamic imports with the **page's**
      availability, unlike `_app`'s own async loader. #100091 chunks those
      imports with `_app`'s own graph and availability, then merges them with
      the page's imports. The generic collector and App Router are untouched.
      The regression was reproduced with
      [dcheng1290/next-loadable-404](https://github.com/dcheng1290/next-loadable-404).
      
      All three backports retain cherry-pick provenance. #100091 had an
      import-only conflict in `pages.rs` because LTS lacks an unrelated
      `smallvec` import; the resolution adds only `FxHashSet`. The
      added/removed lines and test files match upstream. Existing branch
      history is preserved; the merged GTM test fix (#100011) remains
      included.
      
      Fixes #99789 on the LTS line.
      
      ## Verification
      
      With a native binary rebuilt from this LTS backport branch:
      
      - `pages-app-next-dynamic-preload`: **5/5 pass** in Turbopack dev and
      build/start. The suite checks every referenced static asset returns 200,
      the dynamic component renders, and both pages preload the same non-empty
      chunk set.
      - Before applying #100091, the same suite fails **2/5** in Turbopack dev
      on this branch: a non-200 asset and the preload assertion.
      - `pages-app-availability-boundary` and `app-document-import-order`: **3
      pass, 1 existing skip** in Turbopack dev. The upstream gated
      deduplication assertion remains unchanged.
      - `pnpm build-all --env-mode=loose`, `cargo check -p next-api`, `cargo
      fmt -p next-api --check`, scoped Prettier and ESLint pass. The initial
      full bootstrap ran out of sandbox disk during native compilation; after
      clearing disposable artifacts and passing the Cargo environment through
      Turbo, the full build passed.
      
      Earlier verification, before adding #100091, also covered the #99910
      suites in Turbopack start and webpack dev. The new LTS backport has not
      been tested locally in deploy mode, on other platforms, or with full
      workspace type-checking; CI will provide that coverage.
      
      <!-- NEXT_JS_LLM -->
      
      <!-- fleet 652922cb-dc34-493d-9be5-c241a5164cad -->
      
      ---------
      Co-authored-by: 's avatarvercel-fleet-prod[bot] <318278635+vercel-fleet-prod[bot]@users.noreply.github.com>
      Co-authored-by: 's avatarNiklas Mischkulnig <4586894+mischnic@users.noreply.github.com>
      9458fb99
    • Luke Sandberg's avatar
      [lts-active] turbo-tasks snapshot consistency fixes (#99644, #99732, #99649) (#100002) · eb85307e
      Luke Sandberg authored
      ## Summary
      
      Backports three snapshot-consistency fixes to `releases/lts/active`, in
      canary order:
      
      - #99644 turbo-tasks: bincode-encode copy-on-write snapshots instead of
      cloning
      - #99732 turbo-tasks: disable persisting after a failed snapshot
      - #99649 turbo-tasks: copy tasks on their first modification during a
      snapshot
      
      16.4.0 can persist inconsistent task state when a mutation races a
      background snapshot. The main case is #99649. A task that is meta-dirty
      and data-clean when the snapshot starts, then writes data before meta,
      has its live (post-mutation) meta persisted. One example is an
      invalidated task that re-runs while an idle snapshot is writing.
      `children` and `parent_count` are both meta, so the cache on disk can
      list a child edge without the child's matching `parent_count`. `next
      dev` doesn't persist on shutdown, so the next session restores that
      state. When the parent later drops the edge, the server aborts with
      `parent_count underflow: decremented below the number of persistent
      parents`. We have one report of this from a 16.4.0 dev run.
      
      The cherry-picks apply without conflicts. The six touched files are
      identical to `canary` at #99649.
      
      ## Verification
      
      - `cargo test -p turbo-tasks-backend --lib` on this branch: 119 passed.
      This includes #99649's regression test
      `modify_other_category_first_during_snapshot_preserves_snapshot_meta`
      and #99732's `failed_persist_disables_persisting`.
      - Locally on macOS this needed
      `CARGO_TARGET_AARCH64_APPLE_DARWIN_LINKER=cc` and `RUSTFLAGS` set to the
      repo's shared flags without `--icf=all`. The branch's pinned
      `nightly-2026-08-20` ships a `rust-lld` that can't read the current
      macOS SDK's `.tbd` files. This is unrelated to the change, and CI uses
      its normal config.
      
      <!-- NEXT_JS_LLM -->
      
      ---------
      Co-authored-by: 's avatarvercel-fleet-prod[bot] <318278635+vercel-fleet-prod[bot]@users.noreply.github.com>
      Co-authored-by: 's avatarLuke Sandberg <210140+lukesandberg@users.noreply.github.com>
      Co-authored-by: 's avatarTobias Koppers <1365881+sokra@users.noreply.github.com>
      Co-authored-by: 's avatarTobias Koppers <tobias.koppers@googlemail.com>
      eb85307e
    • next-js-bot[bot]'s avatar
      v16.4.1 · 7217011a
      next-js-bot[bot] authored
      7217011a
    • Sebastian Sebbie Silbermann's avatar
      1798e42b
    • Sebastian "Sebbie" Silbermann's avatar
    • Sebastian "Sebbie" Silbermann's avatar
  8. 13 Oct, 2026 1 commit
  9. 12 Oct, 2026 1 commit
  10. 06 Oct, 2026 14 commits
    • next-js-bot[bot]'s avatar
      v16.4.0 · e273d5b2
      next-js-bot[bot] authored
      e273d5b2
    • Jan Kassens's avatar
      [ai-upgrade] discover upgrade models and reasoning efforts from agent CLIs (#99736) · fdf41d6f
      Jan Kassens authored
      The world of AI is moving fast. Instead of hardcoding the available
      models, discover them from the CLIs. This is a bit hacky, but probably
      more reliable than hardcoding a list that will become outdated fast. The
      available models might be different for different accounts.
      
      This involved a bit of code moving as I wanted to have the model
      discovery run in parallel to displaying the user the harness selection
      to reduce delay in selecting the model.
      
      ## Test Plan:
      In addition to new tests, also tested interactively with:
      ```
      DEBUG=next:upgrade node -e \
        "require('./packages/next/dist/lib/upgrade/harness').handoffUpgrade('This is a harness test. Do not modify files.', process.cwd(), null).catch(console.error)"
      ```
      fdf41d6f
    • next-js-bot[bot]'s avatar
      v16.4.0-canary.63 · c3e76ad9
      next-js-bot[bot] authored
      c3e76ad9
    • Will Binns-Smith's avatar
      Document next analyze export in the package bundling guide (#99735) · 47c6cc8d
      Will Binns-Smith authored
      ## Summary
      
      Document `next analyze export` with a snapshot capture/export example
      and a link to its CLI options.
      
      ## Verification
      
      - Prettier and ESLint passed.
      - Runtime tests not run (docs only).
      
      <!-- NEXT_JS_LLM -->
      47c6cc8d
    • Andrew Clark's avatar
      Revert stabilization of `forbidden()` and `unauthorized()` (#99734) · 5b106049
      Andrew Clark authored
      Stabilizing `forbidden()` and `unauthorized()` means the built-in 403
      and 401 fallbacks are rendered into every page's payload, even for apps
      that don't define `forbidden.tsx` or `unauthorized.tsx`. On a fresh
      create-next-app that's about 2.3KB of uncompressed HTML per page (~125
      bytes gzipped).
      
      I knew about the regression but I forgot that it applied to every app
      and every page, rather than just those that use `forbidden.tsx` or
      `unauthorized.tsx`. To avoid blocking the 16.4 release, we'll keep this
      feature in experimental for now until we fix the implementation to
      render the fallbacks lazily.
      
      🤖 Generated with [Claude Code](https://claude.com/claude-code)
      5b106049
    • Josh Story's avatar
      Preserve configured output directories during static export (#99507) · f3a6f976
      Josh Story authored
      ## Summary
      
      Static export with a custom `distDir` currently overwrites that option
      with `.next` during the build. Keep the configured export destination
      intact and derive the intermediate build directory separately, so
      adapters receive the original option while their build-directory
      argument still points to the artifacts.
      
      This removes a post-load config mutation as part of making completed
      configuration immutable for adapters and other runtime consumers.
      Preserve support for both relative and absolute Turbopack project output
      paths.
      
      ## Verification
      
      - Existing adapter tests pass in both production bundlers; custom
      export-directory coverage passes with Turbopack.
      - Existing server trace suite passes with Turbopack: six tests and five
      snapshots.
      - Existing Rust API suite passes its 25 main cases and 15 snapshots in
      each bundler. Its RSS stabilization stress case fails locally on both
      this branch and unmodified canary.
      
      <!-- NEXT_JS_LLM -->
      
      ---------
      Co-authored-by: 's avatarJamiboy Mohammad <jamiboym@gmail.com>
      f3a6f976
    • Will Binns-Smith's avatar
      Rename skill to next-bundle-optimizer and document its usage (#99731) · b22e5a29
      Will Binns-Smith authored
      ## Summary
      
      Rename `next-browser-initial-load-optimizer` to `next-bundle-optimizer`
      and update the skill directory, metadata, links, and install commands.
      
      Document how to use the skill with Turbopack's bundle analyzer, with
      prompts for audits, fixes, and route-specific optimization.
      
      ## Verification
      
      - Prettier passed for the skill and both guides.
      - Runtime tests not run (docs and skill rename only).
      
      <!-- NEXT_JS_LLM -->
      b22e5a29
    • Tobias Koppers's avatar
      [turbo-tasks-backend] Clean up task state before publishing execution completion (#99729) · 74dc549c
      Tobias Koppers authored
      ## What?
      
      Task completion now cleans up the task's per-execution state (removing
      cells that no longer exist, `cleanup_after_execution`) under the same
      task lock that finishes the execution, before the completion is
      published (in-progress state removed, `done_event` notified).
      
      Previously the cleanup ran afterwards, under a second lock acquisition.
      A waiter could invalidate the task in that gap and its next execution
      could start. The old cleanup would then remove that execution's state,
      e.g. the `outdated_*_dependencies` it was just given, and could also
      remove cells it had created.
      
      ## Why?
      
      `collectibles_outdated_dependency` fails locally on canary (5/5 runs
      here) and passes in CI only by timing. Tracing showed the old cleanup
      observing the next collector execution already running with populated
      `outdated_collectibles_dependencies`, then clearing them. Later
      collectible emissions then made the waiting collector stale, so it
      executed an extra time. The optimization from #99386 assumes that
      bookkeeping is intact.
      
      There is a second, independent reason the test can see an extra
      execution: `State::set` invalidates its readers one at a time. The
      collector can then read the source before the source was invalidated,
      see the old collectibles, and legitimately re-execute when the new ones
      arrive.
      
      ## How?
      
      - `task_execution_completed_cleanup` now takes the held `TaskGuard`.
      `task_execution_completed_finish` calls it after setting output and
      immutability, before dropping the guard and notifying `done_event`. The
      canceled path still cleans up, and stale reschedules (including
      `verify_determinism` reruns) still skip cleanup, as before. Removed cell
      data is still dropped outside the critical section.
      - Tests:
      - The existing test is unchanged. Its docs now say it is
      timing-dependent and also covers this cleanup race.
      - A new gated variant stages the overlap explicitly: the collector waits
      until the new emitter execution has started, polls its strongly
      consistent source read to `Pending`, and only then lets the emitter
      emit. This deterministically covers the dirty-not-stale optimization,
      independent of `State` invalidation order.
      
      ## Verification
      
      - With the fix: both tests pass 30/30 locally, and `cargo test -p
      turbo-tasks-backend` passes.
      - Mutant (always stale on collectible change): the gated test fails
      10/10.
      - Known limitation: there is no deterministic regression for the cleanup
      race itself without a backend test hook. With canary's ordering
      restored, the ungated test failed intermittently, between 0/20 and 8/20
      depending on test layout and invocation. The fix was confirmed by
      tracing and by an experiment that widened the old gap.
      - Clippy (default and `verify_serialization,print_cache_item_size`), a
      `verify_determinism` check, and `cargo test -p turbo-tasks-macros-tests`
      pass.
      
      <!-- NEXT_JS_LLM -->
      
      
      <!-- fleet 98a896e8-00fa-4f81-97f0-48bd49e2a9a2 -->
      Co-authored-by: 's avatarvercel-fleet-prod[bot] <318278635+vercel-fleet-prod[bot]@users.noreply.github.com>
      Co-authored-by: 's avatarTobias Koppers <1365881+sokra@users.noreply.github.com>
      Co-authored-by: 's avatarLuke Sandberg <210140+lukesandberg@users.noreply.github.com>
      74dc549c
    • next-js-bot[bot]'s avatar
      v16.4.0-canary.62 · ccf8c15a
      next-js-bot[bot] authored
      ccf8c15a
    • Aurora Scharff's avatar
      Improve static route error guidance (#99724) · b8c7c7f2
      Aurora Scharff authored
      ## Summary
      
      - explain that request-time work conflicts with the route's static
      requirement without repeating “fully static”
      - align the overlay explanations, build messages, and error pages for
      route body, `generateMetadata()`, and `generateViewport()` errors
      - replace the cookie-specific runtime-data card with short browser-data
      pseudocode while preserving its existing docs anchor
      - update the affected build-output snapshots
      
      ## Verification
      
      - `pnpm jest
      packages/next/src/next-devtools/dev-overlay/components/instant/instant-guidance-data.test.ts`
      - formatted and linted all changed source, test, and MDX files
      - Not run: full package build (the isolated worktree reused an older
      dependency install that does not include the latest
      `@base-ui-components/react` packages)
      
      <!-- NEXT_JS_LLM -->
      b8c7c7f2
    • Aurora Scharff's avatar
      docs: add Turbopack experimental config references (#99723) · 81bdd9cb
      Aurora Scharff authored
      ## Summary
      
      - add API references for `turbopackGc`, `turbopackLazyDynamicImports`,
      `turbopackLazyDynamicImportsSSR`, and `turbopackPluginRuntimeStrategy`
      - document each option’s defaults, supported values, runtime behavior,
      and relevant limitations
      - cross-link related Turbopack configuration options
      
      ## Verification
      
      - Verified configuration types and defaults against the current config
      source and Turbopack tests
      - `pnpm prettier --with-node-modules --ignore-path .prettierignore
      --check <new-docs>`
      - `npx eslint --config eslint.config.mjs --fix <new-docs>`
      
      <!-- NEXT_JS_LLM -->
      
      ---------
      Co-authored-by: 's avatarNiklas Mischkulnig <4586894+mischnic@users.noreply.github.com>
      81bdd9cb
    • Jiwon Choi's avatar
      Show choices for agent upgrade prompt (#99727) · fd9c5e93
      Jiwon Choi authored
      show choice for upgrade prompt
      
      | Before | After |
      | --- | --- |
      | <img
      src="https://github.com/devjiwonchoi/next.js/raw/604a56efdcbf2ead22d16c3098ae695eaff7558b/before.png"
      alt="Upgrade prompts before: answered prompts show only the question,
      hint and a blank gap" width="480"> | <img
      src="https://github.com/devjiwonchoi/next.js/raw/604a56efdcbf2ead22d16c3098ae695eaff7558b/after.png"
      alt="Upgrade prompts after: each answered prompt shows the confirmed
      choice" width="480"> |
      fd9c5e93
    • Aurora Scharff's avatar
      docs: add Keeping pages static guide and align the navigation stage docs (#99493) · 3fff1aef
      Aurora Scharff authored
      ## Summary
      
      - add a **Keeping pages static** guide that applies `ensureStatic =
      'shell'`, `'prefetch'`, and `'navigation'` to a store, then works
      through the validation errors and fixes in development
      - expand **Optimizing prefetching** around the App Shell, per-link
      prefetch, and navigation stages, including how `prefetch()` and
      `navigation()` defer cached work
      - align the `ensureStatic`, `instant`, `prefetch()`, and `navigation()`
      references with the guide and clarify how `instant = false` affects
      validation
      - document blocking generation for complete static output in the Cache
      Components ISR guide and update the related migration cross-links
      - add reusable docs-diagram tooling and the uploaded light and dark
      `ensure-static-visual` and `navigation-stage-visual` assets
      
      This PR is stacked on #97801. #99355 has merged.
      
      The Client fix cards, build-output category, and
      `#read-the-data-on-the-client` anchors used by the guide depend on
      #99659 and should land first.
      
      ## Verification
      
      - Prettier and ESLint passed for the latest documentation changes
      through the pre-commit checks
      - `bash -n .agents/skills/docs-diagrams/scripts/render.sh`
      - guide error ordering and route output were checked against development
      and build output
      
      <!-- NEXT_JS_LLM -->
      
      ---------
      Co-authored-by: 's avatarClaude Fable 5.1 <noreply@anthropic.com>
      3fff1aef
    • Benjamin Woodruff ‮'s avatar
      Turbopack: Check the invalidator map before adding a path to a batch (#99711) · 6bcde44e
      Benjamin Woodruff authored
      We don't need to add a file path to a batch and extend the batch
      deadline if the path isn't contained in the invalidator map.
      
      Prevents us from getting logspam like this:
      
      ```
      Turbopack has seen frequent file updates and is waiting for the filesystem to settle (0.5s elapsed so far; last modified: "/Users/bgw/v0/chat/.next/dev/server/next-font-manifest.js").
      ```
      
      This is much less critical with the non-recursive watcher codepath, as
      we're only watching paths we might care about, but keeping it around in
      both cases helps ensure we get some CI coverage of this. I could put it
      behind `#[cfg(debug_assert)]` for non-recursive mode, IDK.
      
      ---------
      Co-authored-by: 's avatarvercel-fleet-prod[bot] <318278635+vercel-fleet-prod[bot]@users.noreply.github.com>
      Co-authored-by: 's avatarTobias Koppers <1365881+sokra@users.noreply.github.com>
      6bcde44e