Dear community,

Apache CouchDB® 3.3.3 has been released and is available for download.

    https://couchdb.apache.org/#download

Pre-built packages for Windows, macOS, Debian/Ubuntu and RHEL/CentOS are 
available.

CouchDB 3.3.3 is a maintenance release, and was originally published on 
2023-12-05.

The community would like to thank all contributors for their part in making 
this release, from the smallest bug report or patch to major contributions in 
code, design, or marketing, we couldn’t have done it without you!

See the official release notes document for an exhaustive list of all changes:

    http://docs.couchdb.org/en/stable/whatsnew/3.3.html

Release Notes highlights:

  - Fix for CVE-2023-45725. The details will be released in seven days. We 
recommend all CouchDB users upgrade.

  - Require authentication for the _replicate endpoint. This is a continuation 
of the 3.x “closed-by-default” security policy.

  - Fix multipart parser "attachment longer than expected” error. Previously 
there was a small chance attachments were not replicated.

  - Various bug fixes related to shard splitting, purging, and replication.

Apache CouchDB® lets you access your data where you need it. The Couch 
Replication Protocol is implemented in a variety of projects and products that 
span every imaginable computing environment from globally distributed 
server-clusters, over mobile phones to web browsers.

Store your data safely, on your own servers, or with any leading cloud 
provider. Your web- and native applications love CouchDB, because it speaks 
JSON natively and supports binary data for all your data storage needs.

The Couch Replication Protocol lets your data flow seamlessly between server 
clusters to mobile phones and web browsers, enabling a compelling offline-first 
user-experience while maintaining high performance and strong reliability. 
CouchDB comes with a developer-friendly query language, and optionally 
MapReduce for simple, efficient, and comprehensive data retrieval.

On behalf of the CouchDB PMC,
Jan Lehnardt
—

Reply via email to