Hi all,

I submit Apache Unomi 4.0.0 release (RC2) to your vote.

RC1 was cancelled. The following corrections and improvements were
done since then:

Migration and compatibility
- UNOMI-996 / UNOMI-997 / UNOMI-998: Finish the 3.0 to 4.0 migration,
  put migrated items in the right tenant, and cover it in ITs
- UNOMI-1001 / UNOMI-1002: Restore 3.0 peer abilities in compatibility
  mode and stop serializing public requests there
- UNOMI-1007 / UNOMI-1008 / UNOMI-1025: Health check env vars, JSON
  shape, timeout, and a configurable tenant for JAAS admin requests
  without a header
- UNOMI-1009 / UNOMI-1010 / UNOMI-1012: Document 4.0 breaking changes
  and compatibility mode

Multi-tenant, tracker, and access control
- UNOMI-1000: Run background tasks for every tenant
- UNOMI-1005 / UNOMI-1013: Restrict visitor cookies and tracker use to
  listed website origins per tenant
- UNOMI-1016: Index API key hashes to tenants in memory
- UNOMI-1019: Document tracker setup per Unomi version, then bundle the
  voted Apache Unomi tracker 2.0.0 (UNOMI-1064 adds the upgrade notes)
- UNOMI-1031: Fail closed when the authorized-IP set for restricted
  event types is empty
- UNOMI-1061: Limit credentialed CORS on admin REST and GraphQL to
  listed origins
- UNOMI-1063: Refuse GraphQL mutations and subscriptions over HTTP GET
- UNOMI-1062: Bound GraphQL query size, depth, and complexity

Aggregates and query correctness
- UNOMI-1014 / UNOMI-1018 / UNOMI-1020 / UNOMI-1021 / UNOMI-1022:
  Return aggregate and metric results in the current tenant, including
  date and range buckets; exact counts on the optimized path; reject
  unsupported date intervals; document IP-range aggregates

Other fixes
- UNOMI-999: Keep scope purge limited to one scope
- UNOMI-1003 / UNOMI-1004: Sort merged segment/scoring lists, fix the
  missing limit, and omit unset optional branches from boolean OR
- UNOMI-1006: Generate a node id per node and run the heartbeat on
  every node
- UNOMI-1026 / UNOMI-1028: Keep migrated schema createdBy on bundle
  re-save, and load built-in types from bundles that start during the
  startup scan
- UNOMI-1030: Copy list membership before GraphQL join/leave updates
- UNOMI-1017: Sum interest points by key when profiles merge
- UNOMI-1065: Handle scorings with no elements when loading dependent
  metadata
- UNOMI-1049: Embed json-patch in the services bundle and stop
  deploying Guava 16
- UNOMI-1011: Stop publishing the empty buildcache jar
- Stabilize two release-build flaky tests (scheduler lock release, and
  cache refresh vs save using a release flag instead of Thread.isAlive)

Plus dependency and tooling bumps, and 4.x branding updates in the
manual and README.

Staging repository:
https://repository.apache.org/content/repositories/orgapacheunomi-1056

Git tag:
unomi-root-4.0.0
https://github.com/apache/unomi/releases/tag/unomi-root-4.0.0

Changes since RC1 (git):
https://github.com/apache/unomi/compare/unomi-root-4.0.0-rc1...unomi-root-4.0.0

Source and binary packages (with .asc and .sha512):
https://dist.apache.org/repos/dist/dev/unomi/4.0.0/

KEYS:
https://dist.apache.org/repos/dist/dev/unomi/KEYS
https://downloads.apache.org/unomi/KEYS

Release notes:
https://issues.apache.org/jira/issues/?jql=project%3DUNOMI%20AND%20fixVersion%3D%22unomi-4.0.0%22

This is a major release. Broader highlights still include multi-tenancy,
OpenSearch persistence, the new clustering/scheduling and caching stack,
removal of OGNL scripting, and the bundled Apache Unomi tracker 2.0.0.

Vote will be open for 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (please indicate why)

Thanks,
Serge

Reply via email to