This is just a security hot-fix for eXist-db 5.3.0 and addresses and closes CVE-2021-44228 by updating log4j to version 2.15.0.
It’s been quite a while since the last release. A lot has been happening behind the scenes, and we are happy to share the outcome with you.
This release is binary compatible with eXist-db 5.2.0.
```xquery xquery version "3.1";
repo:remove("http://exist-db.org/apps/existdb-packageservice"), repo:install-and-deploy("http://exist-db.org/apps/existdb-packageservice", "http://exist-db.org/exist/apps/public-repo/find") ```
|| in attribute and element contentfn:format-number - #3348fn:collection spec compliant - #3349map:remove and array:remove - #3328, #3692controller.xq and controller.xql are now recognized in apps that use eXist's URL Rewriting facility, to conform with the community convention of .xq for main modules and .xqm for library modules.util:base64-encode-url-safe was addedutil:eval to preserve the original error informationA lot of effort was poured into getting eXist-db’s source code licensed properly. It is now consistently LGPL 2.1, with exceptions where code from other projects is used with their permission.
develop branch - #3765guest account not admin - #3288We are very happy to announce that eXist-db 5.2.0 has been released.
5.2.0 is a minor release, and as such should be 100% API compatible with 5.0.0. Whilst this is a fairly conservative release, it fixes two critical issues:
array:put
#3092fn:json-to-xml
#3093FastStringBuffer
#3186isOpen() and close() methods on XML:DB API's
RemoteCollection
#2881fn:subsequence on sequences with atomic
values #3199conf.xml
#3127eXist-db 5.2.0 is binary compatible with previous eXist-db 5.x.x versions back to 5.0.0-RC6. Regardless, before upgrading to this version of eXist-db, it is strongly recommended to perform a full backup and restore. Users who are upgrading should always consult the Upgrading Guide in the documentation. For details of backwards compatibility with versions of eXist-db prior to 5.0.0-RC6, please see the Backwards Compatibility details of 5.0.0-RC6.
exist-db cask.This is a small hotfix release addressing a few important issues.
eXist-db 5.1.1 is binary compatible with eXist-db 5.1.0, 5.0.0, 5.0.0-RC8, 5.0.0-RC7, and 5.0.0-RC6. Regardless, before upgrading to this version of eXist-db, it is strongly recommended to perform a full backup and restore. Users who are upgrading should always consult the Upgrading Guide in the documentation. For details of backwards compatibility with versions of eXist-db prior to 5.0.0-RC6, please see the Backwards Compatibility details of 5.0.0-RC6.
We are very happy to announce that eXist-db 5.1.0 has been released.
5.1.0 is a minor release, and as such should be 100% API compatible with 5.0.0. Whilst this is a fairly conservative release, it fixes two critical issues:
WeakLazyStripes) where under high-load the Garabage Collection of
the old Locks would interfere with the creation of new locks. This
isssue is present in eXist-db 5.0.0 but not 4.7.1. This issue could
cause a 5.0.0 system to throw unexpected exceptions or lock-up.[@attr != value]
#2992SAXSource for included database
documents #3076minimum-must-match on Lucene BooleanQuery
#3107WeakLazyStripes
#3064ConcurrentModificationException at shutdown
#3113ClassNotFoundException for Document Triggers
#2949StackOverflowError caused by lost type into
#3112util:parse-html missing dependency
#3047webdav.properties from the etc directory when available
#3009conf.xml options
#3015eXist-db 5.1.0 is binary compatible with eXist-db 5.0.0, 5.0.0-RC8, 5.0.0-RC7, and 5.0.0-RC6. Regardless, before upgrading to this version of eXist-db, it is strongly recommended to perform a full backup and restore. Users who are upgrading should always consult the Upgrading Guide in the documentation. For details of backwards compatibility with versions of eXist-db prior to 5.0.0-RC6, please see the Backwards Compatibility details of 5.0.0-RC6.
exist-db cask.