Release: Patch 9.1.13

[github-actions]

This is an automated pull request that bumps the version from 9.1.12 to 9.1.13.
Once this pull request is merged, it will trigger a new release of version 9.1.13.
If you're not a core maintainer with permissions to release you can ignore this pull request.

To do

Before merging the PR, there are a few QA steps to go through:

• Add the "freeze" label to this PR, to ensure it doesn't get automatically forced pushed by new changes.
• Add the "ci:daily" label to this PR, to trigger the full test suite to run on this PR.

And for each change below:

1. Ensure the change is appropriate for the version bump. E.g. patch release should only contain patches, not new or de-stabilizing features. If a change is not appropriate, revert the PR.
2. Ensure the PR is labeled correctly with one of: "BREAKING CHANGE", "feature request", "bug", "maintenance", "dependencies", "documentation", "build", "unknown".
3. Ensure the PR title is correct, and follows the format "[Area]: [Summary]", e.g. "React: Fix hooks in CSF3 render functions". If it is not correct, change the title in the PR.
   • Areas include: React, Vue, Core, Docs, Controls, etc.
   • First word of summary indicates the type: “Add”, “Fix”, “Upgrade”, etc.
   • The entire title should fit on a line

This is a list of all the PRs merged and commits pushed directly to next, that will be part of this release:

- [ ] 🔧 Maintenance: Telemetry: Add metadata for react routers #32615

• Nextjs: Fix config access for Vite Nextjs: Fix config access for Vite #32759

If you've made any changes doing the above QA (change PR titles, revert PRs), manually trigger a re-generation of this PR with this workflow and wait for it to finish. It will wipe your progress in this to do, which is expected.

Feel free to manually commit any changes necessary to this branch after you've done the last re-generation, following the Make Manual Changes section in the docs, especially if you're making changes to the changelog.

When everything above is done:

• Merge this PR
• Follow the run of the publish action

---

Generated changelog

9.1.13

- Telemetry: Add metadata for react routers - #32615, thanks shilman!

• Nextjs: Fix config access for Vite - #32759, thanks valentinpalkovic!

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[nx-cloud]

View your CI Pipeline Execution ↗ for commit ee32603

Command	Status	Duration	Result
nx run-many -t build --parallel=3	✅ Succeeded	1m 14s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-10-17 19:09:45 UTC

[vanessayuenn]

Had to do some sneaky stuff to get this patched. The fix PR had to target main as opposed to the typical next, and this broke the typical patch release workflow. Documenting what I did here to workaround that:

1. Merged the fix (Nextjs: Fix config access for Vite #32759) to main
2. Identified a recently patched PR (Telemetry: Add metadata for react routers #32615 in this case), and removed its patch:done label.
3. Manually triggered the prepare patch release workflow
4. The process then tried to again patch that previously patched PR because it's missing patch:done, thus opening this PR containing just the fix PR we want to patch.
5. Manually modified the CHANGELOG and latest.json to not mention the previously patched PR, but instead mention the real fix PR that was merged directly to main.
6. Merge to release the patch as usual.

Thanks for the pointers @JReinhold!