Release: Prerelease 8.0.0-alpha.4 #25189
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
…ion returns null.
Object.keys/Object.values/Object.entries (see screenshot below) don't guarantee maintaining the output order. We're using `for..in` instead to ensure colors swatches are rendered.
API: Remove stories.json support
…-react-automigration
Core: Bundle for node18 in SB8
Addon Docs: Remove `react` peer dependency
CLI: No longer add react in init
…ct-automigration CLI: Add prompt-only automigrate asking for react-removal
…6-sandbox Build: Add sandbox for react-16
Docs: Adds list of available viewports
storybook-bot
force-pushed
the
version-non-patch-from-8.0.0-alpha.3
branch
from
dbfabd5
to
a319460
Compare
SvelteKit: Support 2.0 modules with mocks
|
New, updated, and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: html-webpack-plugin@5.5.3 |
|
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again. Next stepsWhat is new author?A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package. Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights. Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
storybook-bot
force-pushed
the
version-non-patch-from-8.0.0-alpha.3
branch
from
a319460
to
c0ab202
Compare
This is an automated pull request that bumps the version from
8.0.0-alpha.3to8.0.0-alpha.4.Once this pull request is merged, it will trigger a new release of version
8.0.0-alpha.4.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:reactpeer dependency #24881node18#25239react-textarea-autosizetypes #25235<StrictMode />and<Suspense />in source viewer #19785ts-loadervia stricter list ofincludes#24531versionin SvelteKit story #25241 (will also be patched)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.0.0-alpha.4
reactpeer dependency - #24881, thanks @ JReinhold!<StrictMode />and<Suspense />in source viewer - #19785, thanks @ zhyd1997!ts-loadervia stricter list ofincludes- #24531, thanks @ ndelangen!node18- #25239, thanks @ shilman!react-textarea-autosizetypes - #25235, thanks @ ndelangen!