chore(deps-dev): bump immutable from 4.3.0 to 4.3.8 in /ui#7344
chore(deps-dev): bump immutable from 4.3.0 to 4.3.8 in /ui#7344dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps [immutable](https://github.com/immutable-js/immutable-js) from 4.3.0 to 4.3.8. - [Release notes](https://github.com/immutable-js/immutable-js/releases) - [Changelog](https://github.com/immutable-js/immutable-js/blob/main/CHANGELOG.md) - [Commits](immutable-js/immutable-js@v4.3.0...v4.3.8) --- updated-dependencies: - dependency-name: immutable dependency-version: 4.3.8 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
✅ Deploy Preview for odo-docusaurus-preview canceled.
|
|
Hi @dependabot[bot]. Thanks for your PR. I'm waiting for a redhat-developer member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|



Bumps immutable from 4.3.0 to 4.3.8.
Release notes
Sourced from immutable's releases.
... (truncated)
Changelog
Sourced from immutable's changelog.
... (truncated)
Commits
485cbe04.3.86ed4eb6Merge commit from fork94bcd3cfix new proto key injectionfaeb58bfix Prototype Pollution in mergeDeep, toJS, etc.37ca417release 4.3.7 (#2007)23daf26Fix issue with slice negative of filtered sequence (#2006)493afbarelease 4.3.6 (#1997)be3cb9aFix Repeat(<value>).equals(undefined) incorrectly returning true (#1994)d7664bfgenerate sitemap in path that will be deployedf8327b1upgrade next sitemap (#1978)Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for immutable since your current version.
Dependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.