Skip to content

Release: Patch 10.2.18#34127

Closed
github-actions[bot] wants to merge 4 commits into
latest-releasefrom
version-patch-from-10.2.17
Closed

Release: Patch 10.2.18#34127
github-actions[bot] wants to merge 4 commits into
latest-releasefrom
version-patch-from-10.2.17

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

This is an automated pull request that bumps the version from 10.2.17 to 10.2.18.
Once this pull request is merged, it will trigger a new release of version 10.2.18.
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:

  • 🐛 Bug: Core: Fix error reporting in ManagerErrorBoundary #33915
  • 🐛 Bug: Core: Correctly fallback to first detected vitest config file #33865
  • 🏗️ Build: Build: Bump node in .nvmrc file #34079

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:


Generated changelog

10.2.18

  • Core: Correctly fallback to first detected vitest config file - #33865, thanks yannbf!
  • Core: Fix error reporting in ManagerErrorBoundary - #33915, thanks ghengeveld!

ghengeveld and others added 4 commits March 13, 2026 10:27
Core: Fix error reporting in ManagerErrorBoundary
(cherry picked from commit f700486)
…-for-generating-sandboxes

Build: Bump node in .nvmrc file
(cherry picked from commit 8a09a9d)
…ction

Core: Correctly fallback to first detected vitest config file
(cherry picked from commit 943b2b6)
@github-actions github-actions Bot added the release For PRs that trigger new releases. Automated label Mar 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release For PRs that trigger new releases. Automated

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants