Bump immutable from 4.1.0 to 4.3.9 - #168
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps [immutable](https://github.com/immutable-js/immutable-js) from 4.1.0 to 4.3.9. - [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.1.0...v4.3.9) --- updated-dependencies: - dependency-name: immutable dependency-version: 4.3.9 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
ryanio
added a commit
that referenced
this pull request
Aug 24, 2026
## Motivation Five open dependabot PRs, all lockfile-only transitive bumps, all currently red because they were branched before the Forge CI fix in #175. They also all edit the same two lockfiles, so merging them one at a time forces the rest to rebase and burns a CI run each time. Bundling them means one review and one CI run instead of five. Supersedes #168, #169, #170, #171 and #172. Dependabot's commits are cherry-picked unchanged, so authorship and the advisory trail are preserved. | PR | Bump | Advisory | | --- | --- | --- | | #172 | brace-expansion 2.0.1 to 2.1.4 | GHSA-mh99-v99m-4gvg, CVE-2026-13149 (ReDoS) | | #170 | pbkdf2 3.1.2 to 3.1.6 | CVE-2025-6545, CVE-2025-6547 (predictable key material) | | #168 | immutable 4.1.0 to 4.3.9 | GHSA-v56q-mh7h-f735, GHSA-xvcm-6775-5m9r, CVE-2026-29063 | | #169 | immutable 4.1.0 to 4.3.9, vendored OZ copy | as above | | #171 | min-document 2.19.0 to 2.19.2, vendored OZ copy | transitive | ## Solution Two files change and both are lockfiles. No `package.json`, no contract source, no submodule. None of these five packages appears in this repo's `dependencies` or `devDependencies`, so every one is transitive. `yarn.lock` is not published to npm, so no consumer of the package is affected. The Solidity dependencies come from the git submodules in `.gitmodules` rather than npm, so the contracts are untouched. `src-upgradeable/lib-upgradeable/utility-contracts/lib/openzeppelin-contracts/package-lock.json` is a vendored copy of OpenZeppelin, not a submodule, and nothing in the build reads that lockfile. Those two entries (#169 and #171) are inert, and are included here to close out the queue rather than because they change behavior. ## Verification Resolved versions after bundling: ``` yarn.lock brace-expansion 2.1.4 pbkdf2 3.1.6 immutable 4.3.9 vendored OZ lock immutable 4.3.9 min-document 2.19.2 ``` All five cherry-picks applied without conflict, and the diff against `main` touches nothing but the two lockfiles. --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Contributor
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps immutable from 4.1.0 to 4.3.9.
Release notes
Sourced from immutable's releases.
... (truncated)
Changelog
Sourced from immutable's changelog.
... (truncated)
Commits
5da79194.3.9794a1a9Merge commit from fork3dd7e56perf(Map): index large hash-collision buckets for faster lookups62d0b58fix ts in tests8c0e5f8Merge commit from forkf0bc997Merge commit from fork8ac83f4change tagf7373e5use id-token to deploy 4.x version2f545adchangelog485cbe04.3.8Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for immutable since your current version.
You can trigger a rebase of this PR 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.