Metadata title won't update if serverActions is enabled

[bgwastu]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Pro
    Binaries:
      Node: 20.2.0
      npm: N/A
      Yarn: N/A
      pnpm: 8.6.3
    Relevant packages:
      next: 13.4.8-canary.1
      eslint-config-next: 13.4.7
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.3

Which area(s) of Next.js are affected? (leave empty if unsure)

No response

Link to the code that reproduces this issue or a replay of the bug

https:/bagaswastu/next-route-reproduction

To Reproduce

1. Clone the project
2. run pnpm run dev
3. Click on "Go to /test"
4. Browser title is changed to "Test Page"
5. Click on "Go to index"
6. Browser title still on "Test Page" when it's should be changed to "Index"
7. Disable serverActions by changing the value from next.config.js, and see the expected behavior

Note:

• The bug is tested on two different browsers (Chrome and Edge Chromium)
• The <title> tag is changing, but the change is not reflective to the browser unless user performs a browser refresh (F5)

Describe the Bug

The metadata title won't updated after going to another route if serverActions is enabled.

Expected Behavior

The title is changed based on configured metadata.

Which browser are you using? (if relevant)

Latest Chrome Version 114.0.5735.134 (Official Build) (64-bit), fresh from installation with default setting. No extension or modification

How are you deploying your application? (if relevant)

No response

[shuding]

Duplicate of #49409.

[github-actions]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.