1. 11 Dec, 2025 4 commits
    • vercel-release-bot's avatar
      v15.1.10 · 1cfdb45f
      vercel-release-bot authored
      1cfdb45f
    • Hendrik Liebau's avatar
      Update React Version (#45) · 84f00616
      Hendrik Liebau authored
      Co-authored-by: 's avatarJosh Story <story@hey.com>
      84f00616
    • Josh Story's avatar
      Update React Version (#34) · c29b5bd5
      Josh Story authored
      c29b5bd5
    • Zack Tanner's avatar
      Backport Next.js changes to v15.1.10 (#27) · 6e9b2f82
      Zack Tanner authored
      * remove urlencoded server action handling (#14)
      
      * remove urlencoded server action handling
      
      * urlencoded POSTs should still flow through action handler
      
      * bailout early for urlencoded
      
      * tweak handling to 404 in feetch action case
      
      * error when there are no server actions (#15)
      
      * remove custom error
      
      * remove dev gate
      
      * error when there are no server actions
      
      * gate against dev
      
      * Check whether action ids are valid before parsing (#16)
      
      * Check whether action ids are valid before parsing
      
      In an effort to narrow access to parsing methods Next.js now prequalifies MPA form parsing by ensuring there are only valid action IDs as part of the submission. This is not meant to be a strong line of defense against malicious payloads since action IDs are not private and are for many apps relatively easy to acquire. It does however provide some limited narrowing of code paths so that action decoding only happens for plausible actions
      
      Additionally all other branches that use next-action header now consistently check the header before proceeding with parsing. This is also a perf improvement.
      
      * fix test assertion
      
      ---------
      Co-authored-by: 's avatarZack Tanner <1939140+ztanner@users.noreply.github.com>
      
      * fix test
      
      ---------
      Co-authored-by: 's avatarJosh Story <story@hey.com>
      6e9b2f82
  2. 10 Dec, 2025 1 commit
  3. 03 Dec, 2025 4 commits
  4. 22 May, 2025 2 commits
  5. 17 Feb, 2025 2 commits
  6. 11 Feb, 2025 1 commit
  7. 10 Feb, 2025 6 commits
  8. 22 Jan, 2025 3 commits
  9. 20 Jan, 2025 1 commit
    • Janka Uryga's avatar
      fix: don't memory-leak promises passed to `waitUntil` (#75041) · 20f5a79c
      Janka Uryga authored
      ### Overview
      
      `next start` stores pending promises passed to `waitUntil` so that we
      can await them before a (graceful) server shutdown and avoid
      interrupting work that's still running.
      The problem here was that this set lives a long time (the whole lifetime
      of the server), but we weren't removing resolved promises from this set,
      so we'd end up holding onto them forever and leaking memory.
      
      This bug would be triggered by any code using `waitUntil` in `next
      start` (notably, a recent change:
      https://github.com/vercel/next.js/pull/74164)
      
      ### Details 
      The bug here is that `AwaiterMulti` would hold onto resolved promises
      indefinitely. `AwaiterMulti` ends up being used by
      `NextNodeServer.getInternalWaitUntil`, which is what provides
      `waitUntil` in `next start`.
      
      The code was already attempting to clean up promises to avoid leaks. But
      the problem was that we weren't adding `promise` to `this.promises`, we
      were adding `promise.then(...)` which is a completely different object.
      So the `this.promises.delete(promise)` that `cleanup` did was
      effectively doing nothing, and `this.promises` would keep growing.
      20f5a79c
  10. 17 Jan, 2025 10 commits
  11. 07 Jan, 2025 6 commits