chore(deps): bump immutable from 3.8.2 to 4.3.9 - #7974
Open
dependabot[bot] wants to merge 3 commits into
Open
Conversation
Bumps [immutable](https://github.com/immutable-js/immutable-js) from 3.8.2 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@v3.8.2...v4.3.9) --- updated-dependencies: - dependency-name: immutable dependency-version: 4.3.9 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
✅ Deploy Preview for decap-cms ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Bumping immutable to 4.3.9 broke the build and silently corrupted entry data. This adapts the codebase to the new behaviour and type definitions. Runtime fixes: - immutable 4's `mergeDeep` concatenates Lists instead of merging them by index, even when both sides are the same List instance. Because `serializeEntryValues` merged the serialized data back over the original values with `mergeDeep`, every save of an entry with a list field duplicated its items, growing on each save. A shallow `merge` is correct here: `serializedData` already holds the fully recursed value for each known field, so only unknown fields need preserving. - The same hazard applied to `fieldsMetaData` in the entry draft reducer, which relation widgets populate with entry data that can contain lists. Replaced `mergeDeepIn` with a merge that recurses Maps but replaces any other value, matching immutable 3's observable behaviour. Type fixes for the stricter definitions (`getIn` returning `unknown`, `get`/`find` returning `V | undefined`, `fromJS`/`toJS` no longer resolving through the `StaticallyTypedRecord` shim, and precise literal key inference from `Map(obj)`). Also fixes two latent bugs the stricter types exposed: - `hasIntegration` wrapped its argument in `fromJS`, but `getIntegrations` has taken a plain `CmsConfig` since #4960, so it always returned false and disabled the `list-entries` integration check added in #4849. - `MediaLibraryInstance.show` declared `config` as an immutable record, but the caller passes `config.toJS()` and every implementation spreads it as a plain object. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
immutable 4's `fromJS` recurses into any iterable, where immutable 3 only descended into plain objects and arrays. `unsentRequest` ran the whole request object through `fromJS`, so a `FormData` body - which is iterable - was converted into a Map, and the `toJS()` in `toFetchArguments` then handed `fetch` a plain object instead of the original body. Bitbucket is the only backend that sends a `FormData` body, which is why every Bitbucket write failed: media upload, entry persist and delete. The other backends send JSON strings and were unaffected. Convert only `params` and `headers`, the two keys the request helpers actually traverse, and pass every other value through by reference. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
martinjagodic
requested review from
yanthomasdev
and removed request for
a team
September 4, 2026 09:12
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 3.8.2 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.
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.