Skip to content

DOCSP-29819: type regression issue fixed in 4.8.1 #688

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 17, 2023
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions source/whats-new.txt
Original file line number Diff line number Diff line change
Expand Up @@ -372,6 +372,13 @@ To learn more, see `v4.9.0 Release Highlights <https://github.com/mongodb/node-m
What's New in 4.8
-----------------

.. important:: Upgrade from v4.8.0 to v4.8.1

Version 4.8.1 includes a fix to a type regression issue that was
introduced in v4.8.0. By upgrading to v4.8.1, you can specify ``_id``
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion

Language tightening

Suggested change
Version 4.8.1 includes a fix to a type regression issue that was
introduced in v4.8.0. By upgrading to v4.8.1, you can specify ``_id``
Version 4.8.1 fixes a type regression issue
introduced in v4.8.0. By upgrading to v4.8.1, you can specify ``_id``

values and sub-documents when performing updates with the ``$set`` or
``$setOnInsert`` operators.

New features of the 4.8 {+driver-short+} release include:

- Added auto-completion and type safety for nested keys in an update filter
Expand Down