Skip to content

Version Packages #79970

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Version Packages #79970

wants to merge 1 commit into from

Conversation

vercel-release-bot
Copy link
Collaborator

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to canary, this PR will be updated.

Releases

[email protected]

Patch Changes

  • #79302 aa7d4de Thanks @unstubbable! - Enable ppr when dynamicIO is enabled

  • #79565 e0d4df2 Thanks @wyattjoh! - Resolved bug where hitting the parameterized path directly would cause a fallback shell generation instead of just rendering the route with the parameterized placeholders.

  • #79248 21e4411 Thanks @ijjk! - Fix dangling promise in unstable_cache

  • #79213 0c0262e Thanks @unstubbable! - Always pass implicit/soft tags into the CacheHandler.get method

  • #79144 d16d9f4 Thanks @devjiwonchoi! - [TypeScript Plugin] Match method signature (someFunc(): void) type for client boundary warnings.

  • #79204 8eaf44b Thanks @devjiwonchoi! - Fixed rewrite params of the interception routes not being parsed correctly in certain deployed environments

  • #79299 e2837fb Thanks @unstubbable! - Use onPostpone to determine if segment prefetch is partial

  • #79193 3ecf087 Thanks @devjiwonchoi! - [TypeScript Plugin] Moved the diagnostics' positions to the prop's type instead of the value for client-boundary warnings.

  • #79658 c513008 Thanks @eps1lon! - [dev-overlay] Show error overlay on any thrown value

    We used to only show the error overlay on thrown values with a stack property.
    On other thrown values we kept the overlay collapsed.

  • #79448 8751df4 Thanks @unstubbable! - [Segment Cache] Fix: Ensure server references can be prerendered

  • #79109 854992f Thanks @eps1lon! - Sourcemap errors during prerender if experimental.enablePrerenderSourceMaps is enabled

  • #79657 1f25118 Thanks @unstubbable! - Fix name tracking for closures in server actions transform

  • #78882 5136f8e Thanks @unstubbable! - [dynamicIO] Avoid timeout errors with dynamic params in "use cache"

@next/[email protected]

@github-actions github-actions bot added the created-by: CI Used to check if the PR was created during CI label May 30, 2025
@ijjk ijjk added CI approved Approve running CI for fork type: next labels May 30, 2025
@ijjk
Copy link
Member

ijjk commented May 30, 2025

Failing test suites

Commit: 0583bae

pnpm test-start-turbo test/e2e/app-dir/segment-cache/client-only-opt-in/client-only-opt-in.test.ts (turbopack)

  • segment cache prefetch scheduling > prefetches a dynamic page (without PPR enabled)
Expand output

● segment cache prefetch scheduling › prefetches a dynamic page (without PPR enabled)

thrown: "Exceeded timeout of 120000 ms for a test.
Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout."

  89 |   })
  90 |
> 91 |   it('prefetches a dynamic page (without PPR enabled)', async () => {
     |   ^
  92 |     let act: ReturnType<typeof createRouterAct>
  93 |     const browser = await next.browser('/', {
  94 |       beforePageLoad(p: Playwright.Page) {

  at it (e2e/app-dir/segment-cache/client-only-opt-in/client-only-opt-in.test.ts:91:3)
  at Object.describe (e2e/app-dir/segment-cache/client-only-opt-in/client-only-opt-in.test.ts:5:1)

Read more about building and testing Next.js in contributing.md.

@devjiwonchoi devjiwonchoi deleted the changeset-release/canary branch May 30, 2025 13:22
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 14, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
CI approved Approve running CI for fork created-by: CI Used to check if the PR was created during CI locked type: next
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants