chore: update dependency bson to v6 (master) - autoclosed #756
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.
This PR contains the following updates:
^1.1.6->^6.10.3Release Notes
mongodb/js-bson (bson)
v6.10.3Compare Source
Bug Fixes
v6.10.2Compare Source
Bug Fixes
v6.10.1Compare Source
Bug Fixes
Performance Improvements
v6.10.0Compare Source
Features
Bug Fixes
v6.9.1Compare Source
The MongoDB Node.js team is pleased to announce version 6.9.1 of the
bsonpackage!Release Notes
useBigInt64is enabledAfter refactoring to improve deserialization performance in #649, we inadvertently introduced a bug that manifested when deserializing
Longvalues with theuseBigInt64flag enabled. The bug would lead to negativeLongvalues being deserialized as unsigned integers. This issue has been resolved here.Thanks to @rkistner for reporting this bug!
Bug Fixes
Documentation
We invite you to try the
bsonlibrary immediately, and report any issues to the NODE project.v6.9.0Compare Source
Features
tandito Timestamp (#704) (b766d0f)Performance Improvements
v6.8.1Compare Source
The MongoDB Node.js team is pleased to announce version 6.8.1 of the
bsonpackage!Release Notes
useBigInt64is enabledAfter refactoring to improve deserialization performance in #649, we inadvertently introduced a bug that manifested when deserializing
Longvalues with theuseBigInt64flag enabled. The bug would lead to negativeLongvalues being deserialized as unsigned integers. This issue has been resolved here.Bug Fixes
Documentation
We invite you to try the
bsonlibrary immediately, and report any issues to the NODE project.v6.8.0Compare Source
Features
Performance Improvements
v6.7.1Compare Source
The MongoDB Node.js team is pleased to announce version 6.7.1 of the
bsonpackage!Release Notes
useBigInt64is enabledAfter refactoring to improve deserialization performance in #649, we inadvertently introduced a bug that manifested when deserializing
Longvalues with theuseBigInt64flag enabled. The bug would lead to negativeLongvalues being deserialized as unsigned integers. This issue has been resolved here.Bug Fixes
Documentation
We invite you to try the
bsonlibrary immediately, and report any issues to the NODE project.v6.7.0Compare Source
Features
Bug Fixes
v6.6.1Compare Source
The MongoDB Node.js team is pleased to announce version 6.6.1 of the
bsonpackage!Release Notes
useBigInt64is enabledAfter refactoring to improve deserialization performance in #649, we inadvertently introduced a bug that manifested when deserializing
Longvalues with theuseBigInt64flag enabled. The bug would lead to negativeLongvalues being deserialized as unsigned integers. This issue has been resolved here.Bug Fixes
Documentation
We invite you to try the
bsonlibrary immediately, and report any issues to the NODE project.v6.6.0Compare Source
Features
Bug Fixes
v6.5.1Compare Source
The MongoDB Node.js team is pleased to announce version 6.5.1 of the
bsonpackage!Release Notes
useBigInt64is enabledAfter refactoring to improve deserialization performance in #649, we inadvertently introduced a bug that manifested when deserializing
Longvalues with theuseBigInt64flag enabled. The bug would lead to negativeLongvalues being deserialized as unsigned integers. This issue has been resolved here.Thanks to @rkistner for reporting this bug!
Bug Fixes
Documentation
We invite you to try the
bsonlibrary immediately, and report any issues to the NODE project.v6.5.0Compare Source
Features
Bug Fixes
v6.4.1Compare Source
The MongoDB Node.js team is pleased to announce version 6.4.1 of the
bsonpackage!Release Notes
useBigInt64is enabledAfter refactoring to improve deserialization performance in #649, we inadvertently introduced a bug that manifested when deserializing
Longvalues with theuseBigInt64flag enabled. The bug would lead to negativeLongvalues being deserialized as unsigned integers. This issue has been resolved here.Fixed float byte-wise handling on big-endian systems
A change in [email protected] (2024-02-29) started parsing and serializing floats using a
Float64Array. When reading the bytes from this array the ordering is dependent on the platform it is running on and we now properly account for that ordering.Bug Fixes
Documentation
We invite you to try the
bsonlibrary immediately, and report any issues to the NODE project.v6.4.0Compare Source
Features
Bug Fixes
Performance Improvements
v6.3.0Compare Source
Features
v6.2.0Compare Source
Features
Bug Fixes
v6.1.0Compare Source
Features
Bug Fixes
v6.0.0Compare Source
⚠ BREAKING CHANGES
Features
Bug Fixes
v5.5.1Compare Source
The MongoDB Node.js team is pleased to announce version 5.5.1 of the
bsonpackage!Release Notes
Clarify BSONVersionError message
Previously, our thrown
BSONVersionErrorstated that the "bson type must be from 6.0 or later". Our intention is to prevent cross-major BSON types from reaching the serialization logic as breaking changes to the types could lead to silent incompatibilities in the serialization process. We've updated the message to make that intention clear: "bson types must be from bson 6.x.x".Bug Fixes
Documentation
We invite you to try the
bsonlibrary immediately, and report any issues to the NODE project.v5.5.0Compare Source
The MongoDB Node.js team is pleased to announce version 5.5.0 of the
bsonpackage!Release Notes
This release is focused on a bug fix and a new feature for our
Decimal128class.Decimal128constructor andDecimal128.fromStringnow throw when detecting loss of precisionPrior to this release,
Decimal128would round numbers with more than 34 significant digits and lose precision. Now, on detecting loss of precision,Decimal128's constructor andDecimal128.fromStringwill throw aBSONError. This behaviour should have been the default as theDecimal128class was always intended to be high-precision floating point value. As such, silently performing inexact rounding is undesirable behaviour.New
Decimal128.fromStringWithRoundingstatic methodWe understand that some of our users may have depended on the rounding behaviour of
Decimal128.fromStringfor their applications. To support these users, we have exposed this behaviour via theDecimal128.fromStringWithRoundingmethod. Anywhere thatDecimal128.fromStringwas used with the expectation that rounding would occur can be replaced with a call to this new method.We also want to express our gratitude to @hconn-riparian for reporting a related rounding bug and fix in #560 which has been included in our implementation of this feature.
Read more about inexact rounding and the rationale for this change in our
Decimal128specification.Features
Bug Fixes
Documentation
We invite you to try the
bsonlibrary immediately, and report any issues to the NODE project.v5.4.0Compare Source
Features
Bug Fixes
v5.3.0Compare Source
Features
Bug Fixes
v5.2.0Compare Source
Features
v5.1.0Compare Source
Features
5.0.1 (2023-02-16)
Bug Fixes
v5.0.1Compare Source
v5.0.0Compare Source
v4.7.2Compare Source
The MongoDB Node.js team is pleased to announce version v4.7.2 of the bson package!
Bug Fixes
Documentation
We invite you to try the bson library immediately, and report any issues to the NODE project.
v4.7.1Compare Source
The MongoDB Node.js team is pleased to announce version v4.7.1 of the bson package!
Bug Fixes
Documentation
We invite you to try the bson library immediately, and report any issues to the NODE project.
v4.7.0Compare Source
Features
4.6.5 (2022-07-07)
Bug Fixes
__proto__well in EJSON (#506) (4bda57d)4.6.4 (2022-05-19)
4.6.3 (2022-04-20)
4.6.2 (2022-03-22)
Bug Fixes
4.6.1 (2022-01-06)
Bug Fixes
v4.6.5Compare Source
v4.6.4Compare Source
v4.6.3Compare Source
v4.6.2Compare Source
v4.6.1Compare Source
v4.6.0Compare Source
Features
Bug Fixes
4.5.4 (2021-11-03)
Bug Fixes
4.5.3 (2021-10-05)
Bug Fixes
4.5.2 (2021-09-14)
Bug Fixes
4.5.1 (2021-08-24)
Bug Fixes
v4.5.4Compare Source
v4.5.3Compare Source
v4.5.2Compare Source
v4.5.1Compare Source
v4.5.0Compare Source
Features
Timestamp()constructor overload (#449) (0298dd8)Bug Fixes
4.4.1 (2021-07-06)
Bug Fixes
v4.4.1Compare Source
v4.4.0Compare Source
Features
Bug Fixes
__proto__properties (#431) (f34cabc)v4.3.0Compare Source
Features
4.2.3 (2021-03-02)
Bug Fixes
allow library to be loaded in web workeds (#423) (023f57e)
make inspection result of BSON types evaluable (#416) (616665f)
permit BSON types to be created without new (#424) (d2bc284)
4.2.2 (2020-12-01)
Bug Fixes
4.2.1 (2020-12-01)
Bug Fixes
v4.2.3Compare Source
v4.2.2Compare Source
v4.2.1Compare Source
v4.2.0Compare Source
Features
Bug Fixes
v4.1.0Compare Source
Bug Fixes
Features
4.0.4 (2020-03-26)
Bug Fixes
symboltostringifpromoteValuesis true (067a7ba)4.0.3 (2020-01-09)
Bug Fixes
4.0.2 (2019-03-08)
Bug Fixes
ObjectID(ba98ccb), closes #303EJSON.stringify(9f43809), closes #303 #302 #3034.0.1 (2018-12-06)
Bug Fixes
v4.0.4Compare Source
Bug Fixes
symboltostringifpromoteValuesis true (067a7ba)v4.0.3Compare Source
Bug Fixes
v4.0.2Compare Source
Bug Fixes
ObjectID(ba98ccb), closes #303EJSON.stringify(9f43809), closes #303 #302 #303v4.0.1Compare Source
Bug Fixes
v4.0.0Compare Source
Migration Guide
Please see the migration guide for detailed discussion of breaking changes in this release.
Bug Fixes
Numberin relaxed mode (a767fa1)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.