deps: Bump immutable range to ^4.0.0, from ^4.0.0-rc.15

[chrisbobbe]

This way, we'll get new 4.x releases when we do yarn upgrade.

The list of changes since 4.0.0-rc.15 is very short:
https://github.com/immutable-js/immutable-js/releases/tag/v4.0.0

"""

• Ensure latest version docs are built by @leebyron in [Android] Fix: autocomplete popup is not visible. #1877

• Add correct types for empty Seq and Collection by @leebyron
  in Better handling of Keyboard on DrawerOpen. #1878

• keep sidebar fixed + merge top and bottom sidebar by @jdeniau
  in Delete drafts on sending message. #1868

• Changelog 4.0.0 by @bdurrer in Reevaluate and improve the APP_REFRESH action #1880
  """

[gnprice]

Thanks! Change looks good -- comments only on the commit message.

• It looks like there are live GitHub @-mentions in there; best to avoid those: https://github.com/zulip/zulip-mobile/blob/main/docs/style.md#mentioning-people

  Since you're quoting something with @-mentions in it, one solution would be to indent four spaces instead of two, so that GitHub treats it as verbatim text. … In fact, that would also be good for avoiding references like #1877 being interpreted as referring to this repo's issue/PR of the same number.

• The summary says "from ^4.0.0-rc.15", but it looks like we actually have ^4.0.0-rc.12.

• OTOH, the actual version in yarn.lock is already 4.0.0. So we don't even need to consider what the changes are since 4.0.0-rc.12 or 4.0.0-rc.15 -- the change is safe regardless.

• "This way, we'll get new 4.x releases when we do yarn upgrade." -- Is this true? I'd have thought that ^4.0.0-rc.whatever permitted any non-prerelease 4.x release.

  And in fact (from git lsp -G immutable package.json yarn.lock), it seems like db7a18f / Migrate from Unimodules to Expo Modules #5203 did just that 🙂 , taking us to 4.0.0 with a yarn upgrade.

[chrisbobbe]

And in fact (from git lsp -G immutable package.json yarn.lock), it seems like db7a18f / #5203 did just that 🙂 , taking us to 4.0.0 with a yarn upgrade.

Ah. 😝 I'll go ahead and close this, then. Thanks for the review!