-
-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Release: Prerelease 8.3.0-alpha.11 #28991
Conversation
…node-condition Builder-Vite: Fix 'condition node never be used' warning
…t-npx-spawn CLI: Update spawn options in proxy.ts to support Windows
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
30 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings
The Next.js peer dependency requirement got widened to also support v14.1.0 and up.
…irement Next.js-Vite: Update next and vite-plugin-storybook-nextjs dependencies
0cefd84
to
387d494
Compare
Docs: Clarify requirements of Next.js with Vite
387d494
to
231afe9
Compare
Addon Vitest: Fix tests potentially not existing in non-isolate mode
231afe9
to
c9e5de1
Compare
☁️ Nx Cloud ReportCI is running/has finished running commands for commit c9e5de1. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 2 targetsSent with 💌 from NxCloud. |
This is an automated pull request that bumps the version from
8.3.0-alpha.10
to8.3.0-alpha.11
.Once this pull request is merged, it will trigger a new release of version
8.3.0-alpha.11
.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:
And for each change below:
This is a list of all the PRs merged and commits pushed directly to
next
, that will be part of this release: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
8.3.0-alpha.11