-
-
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: Premajor alpha 8.0.0-alpha.0 #25008
Release: Premajor alpha 8.0.0-alpha.0 #25008
Conversation
StoryShots: Remove addon-storyshots from monorepo
Dependencies: Upgrade monorepo to TS5
…nto new-icon-library
UI: New icon library
Build: Remove StoyStore V6 sandbox templates
The state merging of useAddonState needed a fix because the merger function wasn't called with the correct data, due to react18 using async rendering, making this.state be the old state.
…to norbert/react18
UI: Upgrade manager to react 18
…erface Essentials: Export interface `PresetOptions`
🚨 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
|
Documentation: Add dark-mode migration docs
Build: Updates from merged PRS unto 8-0
e99b73d
to
3508974
Compare
3508974
to
382b90d
Compare
…ybookjs/storybook into version-non-patch-from-7.6.0-beta.2
This is an automated pull request that bumps the version from
7.6.0-beta.2
to8.0.0-alpha.0
.Once this pull request is merged, it will trigger a new release of version
8.0.0-alpha.0
.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:Nope
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.0
Nope