Hi all, First of all let me wish you a happy near year !
Below is a summary of the Unomi monthly dev sync call held on 8 January 2026. As a reminder, this call is intended for communication and synchronization only; no binding decisions are taken during such meetings. Any changes mentioned are either already reflected in Jira issues or pull requests, or will continue to be discussed on the mailing list as appropriate. ⸻ Meeting details • Date: 8 January 2026 • Time: 17:00–17:35 (Europe/Zurich) ⸻ Topics discussed Technical issues & fixes Item ID suffix issue • An issue was identified where a suffix is added to item IDs in Elasticsearch, causing problems for custom items that are not refreshed regularly. • This mainly affects migrated items that are not overridden (e.g. custom conditions). • Serge mentioned that a correction script already exists and that a Jira ticket will be used to track the fix to the migration process. Health check configuration • Jérôme confirmed that the health check is currently disabled by default. • A pull request was opened to re-enable it in the relevant configuration files, referencing the same tracking ticket [PR-748]. Number of visits • Jérôme shared that the fix for the “number of visits” feature has been committed, reviewed, and merged. • The implementation includes: • Number of visits (affected by purge), • Total visits (historical count). • Migration scripts and tests are included. • There is currently no urgency to trigger a release specifically for this change. ⸻ Git workflow & repository management Merge history issues • Serge shared feedback from recent cleanup work where lost merge history resulted in a large number of manual conflict resolutions (around 600 files). • Different merge tools were tested, with Araxis giving better results in this context. • A proposal to restrict merge strategies using ASF GitHub configuration was discussed; a corresponding pull request was created and is tracked on GitHub [PR-747]. Pull requests • Jérôme opened a pull request to reactivate the health check [PR-748], which has since been reviewed. • François opened a pull request proposing updated GitHub merge settings [PR-747], which is now available for broader review and discussion on the list. ⸻ Unomi-3-dev branch status Serge’s update • All unit, integration, and API tests are currently passing on unomi-3-dev. • Recent commits from Jérôme were merged, with some complexity due to branch history. • OpenSearch was upgraded to version 3.4 and validated through tests. • An issue was identified and fixed in the persona sessions API (previously little-used). • Custom tooling was developed to help split a large codebase (1000+ chunks) into reviewable pull requests. • The branch is now ready for progressive PR submissions to the community. ⸻ Project & ecosystem updates Production usage • Serge shared that Unomi 3.1 core functionality is complete for current SaaS project needs. • Kubernetes-based infrastructure work is ongoing. • OpenSearch is currently planned for production usage, notably for ML-related capabilities. Elasticsearch version alignment • Jérôme mentioned aligning the Elasticsearch version with the one used internally at his company. ⸻ Administrative notes • The latest board report has been submitted. • A reminder was made that +1 replies on the mailing list are helpful to demonstrate activity and engagement for the project. ⸻ References • [PR-747] GitHub merge strategy configuration proposal https://github.com/apache/unomi/pull/747 • [PR-748] Reactivate health check https://github.com/apache/unomi/pull/748 ⸻ If anything was missed or needs clarification, please follow up on the list. Thanks everyone, Serge
