Skip to content

build(deps): bump immutable from 5.1.9 to 5.2.1 - #560

Merged
github-actions[bot] merged 1 commit into
masterfrom
dependabot/npm_and_yarn/immutable-5.2.1
Nov 13, 2026
Merged

github-actions[bot] merged 1 commit into
masterfrom
dependabot/npm_and_yarn/immutable-5.2.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 13, 2026

Copy link
Copy Markdown
Contributor

Bumps immutable from 5.1.9 to 5.2.1.

Release notes

Sourced from immutable's releases.

v5.2.1

What's Changed

Full Changelog: immutable-js/immutable-js@v5.2.0...v5.2.1

v5.2.0

What's Changed

New Contributors

Full Changelog: immutable-js/immutable-js@v5.1.10...v5.2.0

v5.1.10

  • fix(Seq): Incorrect (NaN) keys when iterating in reverse an indexed lazy Sequence of unknown size #2268
  • fix(Seq): Stack overflow when slicing a zipped Sequence of unknown size from the end - by @​b84330808 in immutable-js/immutable-js#2311
  • fix(Seq): Incorrect keys of an interposed Sequence when iterated in reverse - by @​b84330808 in immutable-js/immutable-js#2310
  • fix(Seq): Incorrect keys of a filtered indexed Seq when iterated in reverse - by @​b84330808 in immutable-js/immutable-js#2309
  • fix(Seq): Fix takeLast(0) on a Sequence of unknown size - by @​b84330808 in immutable-js/immutable-js#2313
  • fix(Seq): skipWhile and skipUntil on an indexed Seq now renumber iterator keys from 0, consistently with toArray and entrySeq, and entries() no longer throws once exhausted. This also fixes iterating a chained map/filter and equals on such sequences - by @​wozhenbang2004 in immutable-js/immutable-js#2319
  • [TypeScript]: on a MapOf (a Map built from an object), delete and remove of a required key now give a MapOf without that key (Map({ a: 1, b: 'b' }).delete('b') is a MapOf<{ a: number }>) instead of never. Deleting an optional key still keeps the type. #2312

Doc

  • [TypeScript]: on a MapOf (a Map built from an object), delete and remove of a required key now give a MapOf without that key (Map({ a: 1, b: 'b' }).delete('b') is a MapOf<{ a: number }>) instead of never. Deleting an optional key still keeps the type. #2312

New Contributors

Full Changelog: immutable-js/immutable-js@v5.1.9...v5.1.10

Changelog

Sourced from immutable's changelog.

5.2.1

  • [TypeScript] The functional getIn accepts a key path typed KeyPath again, like the one a wrapper function receives and forwards. It was a type error since 5.2.0; the result is unknown, as in 5.1. #2328 by @​jdeniau
  • [TypeScript] The methods setIn, updateIn, mergeIn, mergeDeepIn, deleteIn, removeIn, the untyped getIn and hasIn, and the functions setIn and removeIn type their key path as KeyPath, which the functions hasIn and updateIn already used: an array-like or an ordered Immutable collection, as the runtime accepts. A path typed KeyPath is now accepted everywhere. A path typed Iterable<…> is now a type error, like an ES6 Set or a generator, which throw Invalid keyPath at runtime: type it KeyPath<…> instead, exported since 5.1.0. #2328 by @​jdeniau

5.2.0

  • Fix keySeq() on a lazy indexed Seq of unknown size in #2325 by kevin9327

[TypeScript] Record#getIn is typed from the Record's properties, like MapOf#getIn

No runtime change. Record#getIn also accepts a notSetValue, as the runtime always did.

const Address = Record({ city: '', zip: 0 });
const Person = Record({ name: '', address: Address() });
const person = Person();
person.getIn(['address', 'city']); // was unknown, now string
person.getIn(['address', 'street']); // was unknown, now a type error: expected one of "city" | "zip"
person.getIn(['address', 'street'], 'nsv'); // was a type error (one argument expected), now 'nsv'

[TypeScript] Record#update(updater) is properly typed

const point = Record({ x: 0, y: 0 })();
point.update((p) => p.x + p.y); // was a type error (two arguments expected), now number

[TypeScript Break] A key path the types can not follow is a type error

For MapOf#getIn, Record#getIn and the functional getIn. Such a path previously gave never, which TypeScript accepted silently, and a valid path needed as const to give its type.

const map = Map({ a: { b: 1 } });
map.getIn(['a', 'b']); // was never (number with ['a', 'b'] as const), now number without as const
map.getIn(['z']); // was never, now a type error: expected one of "a"
map.getIn(['a', 'b', 'c']); // was never, now a type error: no key can be read from number
map.getIn(['z'], 'nsv'); // was never, now 'nsv': with a notSetValue, a key the types do not know is accepted

A path only known at runtime is typed as such, and the result is unknown:

const path: Array<string> = ['a', 'b'];
map.getIn(path); // was never, now unknown
</tr></table>

... (truncated)

Commits
  • 4c18997 5.2.1
  • 1449984 Merge pull request #2328 from jdeniau/getin-forwarded-keypath
  • dc12267 [TypeScript] Type every key path parameter as KeyPath
  • 4844b96 [TypeScript] getIn: accept a key path typed KeyPath
  • 7146ae1 Merge pull request #2326 from immutable-js/release-5.2.0
  • 3e7070b Add changelog for 5.2.0
  • 92e6eaa 5.2.0
  • b39d130 Merge pull request #2324 from jdeniau/typed-record-getin
  • 2de4534 [TypeScript] getIn: follow a nested Record, accept an object key of a Map
  • 4ac12cc [TypeScript] getIn: a key that may be missing and generic collections
  • Additional commits viewable in compare view

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @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)

Bumps [immutable](https://github.com/immutable-js/immutable-js) from 5.1.9 to 5.2.1.
- [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@v5.1.9...v5.2.1)

---
updated-dependencies:
- dependency-name: immutable
  dependency-version: 5.2.1
  dependency-type: indirect
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Nov 13, 2026
@dependabot @github

dependabot Bot commented on behalf of github Nov 13, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: npm. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@github-actions
github-actions Bot enabled auto-merge (squash) November 13, 2026 09:07
@sonarqubecloud

Copy link
Copy Markdown

@github-actions
github-actions Bot merged commit da6775d into master Nov 13, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants