Release: Premajor alpha 8.0.0-alpha.0

[github-actions]

This is an automated pull request that bumps the version from 7.6.0-beta.2 to 8.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:

• 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:

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:

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

---

Generated changelog

8.0.0-alpha.0

Nope

[socket-security]

New, updated, and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
@types/compression	1.7.5	None	+0	10.9 kB	types
@types/tmp	0.2.6	None	+0	10.4 kB	types
@types/color-convert	2.0.3	None	+1	24.7 kB	types
react-transition-group	4.4.5	environment	+1	371 kB	eps1lon
@types/react-transition-group	4.4.9	None	+0	18.5 kB	types
@testing-library/user-event	14.3.0	None	+0	256 kB	testing-library-bot
vue-loader	15.11.1	None	+8	538 kB	soda
@types/webpack-virtual-modules	0.1.2...0.1.3	None	+5/-6	172 kB	types
next	14.0.2...14.0.3	None	+10/-12	1.14 GB	vercel-release-bot
@types/util-deprecate	1.0.0...1.0.3	None	+0/-0	2.9 kB	types
@types/babel__plugin-transform-runtime	7.9.4...7.9.5	None	+0/-0	3.6 kB	types
@types/ip	1.1.1...1.1.3	None	+0/-1	5.86 kB	types
@types/js-yaml	4.0.6...4.0.9	None	+0/-0	9.12 kB
@types/mock-fs	4.13.2...4.13.4	None	+0/-1	14.1 kB	types
@types/prompts	2.4.5...2.4.9	None	+0/-1	7.96 kB	types
@types/jest-specific-snapshot	0.5.7...0.5.9	None	+0/-4	4.23 kB	types
@types/picomatch	2.3.1...2.3.3	None	+0/-0	18 kB	types
@types/webpack-env	1.18.2...1.18.4	None	+0/-0	16.7 kB	types
@angular/cli	16.2.4...16.2.10	None	+5/-8	12.6 MB	google-wombot
@types/ws	8.5.6...8.5.10	None	+0/-1	21.7 kB	types
react-docgen	7.0.0...7.0.1	None	+4/-16	267 kB	danez
@angular/compiler-cli	16.2.7...16.2.12	None	+3/-3	69.4 MB	google-wombot
@angular-devkit/build-angular	16.2.4...16.2.10	None	+22/-112	76.2 MB	google-wombot
@types/jscodeshift	0.11.10...0.11.11	None	+0/-0	38 kB	types
@storybook/theming	7.5.0...7.5.3	None	+0/-0	724 kB	shilman
@storybook/client-logger	7.5.0...7.5.3	None	+0/-0	7.45 kB	shilman
@angular/platform-browser-dynamic	16.2.7...16.2.12	None	+5/-10	40.8 MB	google-wombot
@types/webpack-hot-middleware	2.25.7...2.25.9	None	+2/-11	191 kB	types
vue-template-compiler	2.7.14...2.7.15	None	+0/-0	583 kB	yyx990803
@angular/platform-browser	16.2.7...16.2.12	None	+3/-3	32.7 MB	google-wombot
@angular/common	16.2.7...16.2.12	None	+1/-1	30.2 MB	google-wombot
@angular/animations	16.2.7...16.2.12	None	+1/-1	20.8 MB	google-wombot
@angular/forms	16.2.7...16.2.12	None	+4/-4	34.6 MB	google-wombot
@angular/compiler	16.2.7...16.2.12	None	+1/-1	27.2 MB	google-wombot
@angular/core	16.2.7...16.2.12	None	+0/-0	19.1 MB	google-wombot
@storybook/icons	1.1.7...1.2.2	None	+0/-0	1.16 MB	ndelangen
@preact/preset-vite	2.5.0...2.7.0	None	+6/-16	2.84 MB	jdecroock
svelte-preprocess	5.0.4...5.1.1	None	+2/-12	2.81 MB	dummdidumm
@types/loader-utils	2.0.5...2.0.6	None	+5/-6	176 kB	types
svelte	4.2.1...4.2.7	None	+0/-18	2.63 MB	svelte-admin
@types/npmlog	4.1.4...4.1.6	None	+0/-0	7.46 kB	types
@rollup/pluginutils	5.0.4...5.0.5	None	+0/-2	37.7 kB	shellscape
vue-docgen-api	4.74.2...4.75.1	None	+0/-68	808 kB	vue-styleguidist-bot
jest-preset-angular	13.1.2...13.1.4	None	+28/-236	102 MB	anhpnnd
@vitejs/plugin-vue	4.4.0...4.5.0	None	+0/-3	183 kB	vitebot
preact	10.18.1...10.19.2	None	+0/-0	1.34 MB

🚮 Removed packages: @axe-core/[email protected], @babel/[email protected], @jest/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @types/[email protected], @types/[email protected], @types/[email protected], @types/[email protected], @types/[email protected], @types/[email protected], @types/[email protected], @types/[email protected], @types/[email protected], @types/[email protected], @types/[email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Issue	Package	Version	Note	Source
New author	vue-hot-reload-api	2.3.4	New Author: soda Previous Author: yyx990803	@storybook/[email protected], @storybook/[email protected] via code/package.json [email protected] via code/frameworks/vue-webpack5/package.json [email protected] via code/presets/vue-webpack/package.json
New author	vue-style-loader	4.1.3	New Author: soda Previous Author: yyx990803	@storybook/[email protected], @storybook/[email protected] via code/package.json [email protected] via code/frameworks/vue-webpack5/package.json [email protected] via code/presets/vue-webpack/package.json
New author	loupe	2.3.7	New Author: keithamus Previous Author: chai	@storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @vitest/[email protected], @vitest/[email protected] via code/package.json @vitest/[email protected] via code/lib/instrumenter/package.json @vitest/[email protected], [email protected] via code/lib/test/package.json

Next steps

What 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 dependency

Take 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 package

If 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 risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore [email protected] bar@* or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore [email protected]
• @SocketSecurity ignore [email protected]
• @SocketSecurity ignore [email protected]