-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
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
Bump immer from 8.0.4 to 9.0.6 #11364
Conversation
Bumps [immer](https://github.com/immerjs/immer) from 8.0.4 to 9.0.6. - [Release notes](https://github.com/immerjs/immer/releases) - [Commits](immerjs/immer@v8.0.4...v9.0.6) --- updated-dependencies: - dependency-name: immer dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
This will fix #11443 :) |
Could this be merged already, please? It is pretty straightforward change and it is making my build fail. |
Now this is merge how do I get the update? will react-dev-utils have a version update? |
Bumping @Brycetastic's comment, we're getting a high severity vulnerability alert for this (as I'm sure a lot are) and would like to get it resolved. We're on the latest version of react-scripts (4.0.3) and react-dev-utils (11.0.4) but immer is still 8.0.1 |
Any updates on this? |
how about having 4.0.4 with this one? |
Out of curiosity, is there anyone we need to tag from the admins to check this out? |
Like everyone above mentioned, this code change is not helping us with the vulnerability issue with immer, I am still getting immer@8.0.1. @iansu @mrmckeb @PatrickShaw @ianschmitz @kentcdodds Please let us know what we need to do to resolve this and get the upgraded version of immer in our repo. |
PR already merged, but we haven't seen any new patch on npm, it still uses immer@8.0.1. Do we have a plan to publish this? |
@mrmckeb Could you please give an update on this? |
Facing the same issue, using the latest |
@@ -65,7 +65,7 @@ | |||
"global-modules": "2.0.0", | |||
"globby": "11.0.1", | |||
"gzip-size": "5.1.1", | |||
"immer": "8.0.4", | |||
"immer": "9.0.6", |
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.
There is no change in package.json version that seems to be an issue.
Any updates? |
we are waiting on it please update this? |
@iansu can we get a patch version released to address this vulnerability? |
Any updates on this one? |
downstream, [react-dev-utils v11.x.x](https://www.npmjs.com/package/react-dev-utils/v/11.0.4) is subject to a [vulnerability](GHSA-33f9-j839-rf8h). Since the release of 12.x.x, `immer` [has been bumped up](facebook/create-react-app#11364 (comment)) and should resolve the "critical" security alert if it's adopted into Gatsby.
Bumps immer from 8.0.4 to 9.0.6.
Release notes
Sourced from immer's releases.
... (truncated)
Commits
fa671e5
fix(security): Follow up on CVE-2020-28477 wherepath: [["__proto__"], "x"]
...2e0aa95
Create SECURITY.md050522d
chore: fix CI. maybe.1195510
docs: Update example-setstate.mdx (#833)648d39b
docs: fixing link to RFC-6902 & fixing typo (#830)bc890f7
docs: Update example-setstate.mdx (#829)16a3d0f
chore(deps): bump prismjs from 1.23.0 to 1.24.0 in /website (#822)847492c
docs: Extended / updated documenation (#824)7f41483
chore: [workflows] don't release from forks3f9a94e
chore: let's test before publishDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)@dependabot use these labels
will set the current labels as the default for future PRs for this repo and language@dependabot use these reviewers
will set the current reviewers as the default for future PRs for this repo and language@dependabot use these assignees
will set the current assignees as the default for future PRs for this repo and language@dependabot use this milestone
will set the current milestone as the default for future PRs for this repo and languageYou can disable automated security fix PRs for this repo from the Security Alerts page.