Release: Patch 7.1.1 #23503
Release: Patch 7.1.1 #23503
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Settings: Add What's new? page and remove release notes page
Unit Tests: Fix tests on Windows
…-unit-tests-on-github-actions CI: Remove Ubuntu/Mac Unit Tests on Github Actions
…pm-scope-for-sandboxes CI: Only run Storybook scoped packages via verdaccio
…1.0-alpha.44 Release: Prerelease beta 7.1.0-beta.0
…indows Yarn: Fix pnp package resolution on Windows
…orybook into norbert/fix-21341
SyntaxHighlighter: Expose registerLanguage
|
🚨 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 an install script?Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts. Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead. What is shell access?This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code. Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced. What is eval?Package uses eval() which is a dangerous function. This prevents the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior. Avoid packages that use eval, since this could potentially execute any code. 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-patch-from-7.1.0
branch
6 times, most recently
from
0b18a87
to
28e6ded
Compare
storybook-bot
force-pushed
the
version-patch-from-7.1.0
branch
5 times, most recently
from
ba67a35
to
3a21858
Compare
…mode-in-angular-optional Angular: Make enableProdMode optional (cherry picked from commit 10e38b5)
…ship-file Codeowners: Add file (cherry picked from commit 98432d5)
Docs: fix readme storyshots link (cherry picked from commit f6ee55b)
Chromatic: Fix flaky chromatic tests caused by the next/image component loading (cherry picked from commit 4d2f321)
Update autodoc to proper default value (cherry picked from commit c06e18a)
Release tooling: Fixes from stable promotion (cherry picked from commit 6850a8f)
storybook-bot
force-pushed
the
version-patch-from-7.1.0
branch
from
3a21858
to
fa8b1c8
Compare
This is an automated pull request that bumps the version from
7.1.0to7.1.1.Once this pull request is merged, it will trigger a new release of version
7.1.1.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:🍒 Manual cherry picking needed!
The following pull requests could not be cherry-picked automatically because it resulted in merge conflicts.
For each pull request below, you need to either manually cherry pick it, or discard it by replacing the "patch:yes" label with "patch:no" on the PR and re-generate this PR.
git cherry-pick -m1 -x 5b34161518dd28b2451d2e075688a1c1e75928efgit cherry-pick -m1 -x 779b4f63cef7c9f97b4eac747e29b550714e03c1git cherry-pick -m1 -x 950df76ef306e85a280b98477e8ed41862281b38If 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
7.1.1