Dear colleagues, We just deployed 1.113.2 release to Production. The 1.113.2 release has the following changes: * This release contains the changes related to 1.113 release, explained in the previous email. * We deployed the change from 1.112.1 release to mitigate issues arising from updates with numerous references (validate max references #1486). * Handle Multipart/mixed Bounced and Auto-submitted Messages (#1490). The release notes are on the website: https://apps.db.ripe.net/docs/Release-Notes/#ripe-database-release-1-113-2 Regards Miguel Herrán RIPE NCC On Mon, 17 Jun 2024 at 17:35, Edward Shryane via db-wg <db-wg@ripe.net> wrote:

Dear colleagues,

RIPE Database release 1.113 has been deployed to the Release Candidate environment for testing. We plan to deploy to production on Monday 1st July.

The 1.113 release has the following main changes:

* Inetnum AGGREGATED-BY-LIR status (implements RIPE-822 policy) (#1467) * Enable Client Auth Certificate for REST API lookup (#1475) * ROA Overlapping INVALID ROA and VALID ROA fix (#1470) * Java 21 Support (#1440)

The release notes are on the website: https://apps.db.ripe.net/docs/Release-Notes/#ripe-database-release-1-113

More information on the Release Candidate environment can be found on our website: https://apps.db.ripe.net/docs/Release-Notes/

The data in the RC environment is a dummified copy of production from 12th June.

Please let us know if you find any issues with this release in the RC environment.

Regards Ed Shryane RIPE NCC

--

To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/db-wg