MongoDB 8.2.1 is out and is ready for production deployment. This release contains only fixes since 8.2.0, and is a recommended upgrade for all 8.2 users.
Fixed in this release:
SERVER-94681 Move sampling to the oplog cap maintainer thread
SERVER-106469 Starting mongocryptd fails on latest build, windows.
SERVER-109626 Adjust behavior for emitting additional fields in change streams
SERVER-110250 Use existing session when dropping spill WT ident
WT-15225 Fix newly created table and drop() EBUSY issue
I have downloaded the zip version for windows x64 platform, but after unzipping, when I check the properties > details of the mongod.exe or mongos.exe, it fails the basic information that is required.
I understand that these metadata fields aren’t directly tied to the digital signature or protected attributes. However, it’s worth noting that earlier versions of the binaries did include these fields — such as product name, version, and copyright — which made it easier to verify authenticity and track builds, especially in offline or controlled environments.
While I agree it’s not a strict security requirement, having that metadata adds transparency, improves traceability across releases, and helps teams performing audits or version checks to quickly validate binaries.
It would be great if future builds could restore this metadata for consistency with previous versions and to maintain trust in offline or compliance-sensitive setups.
That’s a really good point. Having those metadata fields definitely helps with version tracking and verification, especially in secure or offline setups. Hopefully the team brings that back in future releases for better consistency and transparency.
