+1 (binding) François [email protected] [email protected]
Le 16/11/2026 à 12:01, Mohamed Tayeb BENTERKI a écrit :
Hello, +1 I checked: - SHA-512 checksums of the source and binary packages match - GPG signatures are valid (key A5011B897E6D7C96EA8D97984B65ABFBFCD57B56, in KEYS) - Source zip matches the unomi-root-3.1.0 git tag (b9eeff962) - LICENSE and NOTICE files are present in the source and binary packages - No unexpected binaries or SNAPSHOT dependencies - Build from source with JDK 17 / Maven 3.9 passes: unit tests and apache-rat:check (0 unapproved files) - Ran the binary distribution against Elasticsearch 9.1.3. Startup was clean with no errors in karaf.log. Version and build number are correct (3.1.0 / b9eef). All healthcheck providers are LIVE, and 20 concurrent healthcheck calls succeeded (UNOMI-924). context.json created a profile and session, and the view event was persisted. Minor, not blocking: the source zip contains .mvn/.develocity/develocity-workspace-id, which isn't in git. It could be excluded from the source assembly in future releases. Thanks Jonathan for running the release! On Mon, 16 Nov 2026 at 10:37, Jonathan Sinovassin-naïk via dev < [email protected]> wrote:Hi all, I submit the Apache Unomi 3.1.0 release to your vote. This release is built from the new unomi-3.x branch. It contains 2 bug fixes and 8 improvements of the 3.0 line. Here are the release notes of the new version: Bug - [UNOMI-924 <https://issues.apache.org/jira/browse/UNOMI-924>] - Impossible to call healthcheck concurrently - [UNOMI-1025 <https://issues.apache.org/jira/browse/UNOMI-1025>] - Healthcheck: restore the provider timeout Improvement - [UNOMI-973 <https://issues.apache.org/jira/browse/UNOMI-973>] - Confine recurrent import/export file endpoints to configurable base directories - [UNOMI-985 <https://issues.apache.org/jira/browse/UNOMI-985>] - Build scans lack current insight data because the Develocity build extensions are out of date - [UNOMI-1050 <https://issues.apache.org/jira/browse/UNOMI-1050>] - Require a login before a GraphQL WebSocket can be used - [UNOMI-1055 <https://issues.apache.org/jira/browse/UNOMI-1055>] - Limit the work done by matchesRegex - [UNOMI-1056 <https://issues.apache.org/jira/browse/UNOMI-1056>] - Use a simpler pattern for request identifiers - [UNOMI-1057 <https://issues.apache.org/jira/browse/UNOMI-1057>] - Use only the personalization contents that passed filtering - [UNOMI-1058 <https://issues.apache.org/jira/browse/UNOMI-1058>] - Keep expression-engine helpers out of scripts - [UNOMI-1060 <https://issues.apache.org/jira/browse/UNOMI-1060>] - Limit diagnostic tracking and the expression cache The "What's new in Apache Unomi 3.1" section of the manual lists the configuration changes to apply before an upgrade from 3.0. Staging Repositories: https://repository.apache.org/content/repositories/orgapacheunomi-1055 You can find the sources here: https://repository.apache.org/service/local/repositories/orgapacheunomi-1055/content/org/apache/unomi/unomi-root/3.1.0/unomi-root-3.1.0-source-release.zip Convenience binaries are also available here: https://repository.apache.org/service/local/repositories/orgapacheunomi-1055/content/org/apache/unomi/unomi/3.1.0 The source and binary packages, with their signatures and SHA-512 checksums, are also in the dist/dev area: https://dist.apache.org/repos/dist/dev/unomi/3.1.0/ Git tag: unomi-root-3.1.0 Release Notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12357799&styleName=&projectId=12319220 Please vote to approve this release: [ ] +1 Approve the release [ ] -1 Don't approve the release (please provide specific comments) This vote will be open for at least 72 hours, or until the necessary number of binding votes (3 +1) is reached. Please let me know if you have any questions. Kind regards, Jonathan
