I’ve stumbled upon this collection when looking for possibly unmaintained collections in ACP 15.0.0a2 because there hasn’t been a new release since Oct 30, 2025.
It looks like the last sanity test / CI run has been on Jun 15. So I think they violate our inclusion requirements.
Additionally, sanity tests are run against devel but not against 2.20 or 2.21.
I’ve opened an issue in their repo to let them know. Maybe this helps 
hello @mariolenz ,
Thanks for flagging this - being part of the Ansible Community Package means a lot to us at RavenDB, and we’re not taking the heads-up lightly.
Here’s what we’ve addressed on main:
CI reactivated. The scheduled workflow was auto-disabled after inactivity; it’s now running on push, PR, and the weekly cron again.
Matrix updated. Sanity + integration jobs now explicitly cover stable-2.20, stable-2.21, stable-2.22, and devel alongside the existing 2.16-2.19 rows.
Previously failing tests fixed:
a. Debian 11 scenario dropped (upstream EOL, apt security mirror pulled packages).
b, Rebuilt our custom RHEL test image on CentOS Stream 9 + Python 3.11 (ansible-core 2.22/devel require Python >=3.10 on target).
c/ Rotated expired test certificates and corrected the setup port used by the secured scenario.
All matrix rows and molecule scenarios are green on the latest main run. We’ll keep an eye on the scheduled runs going forward and treat any Steering Committee flag as a first-class signal.
No release is required since the fixes are pure CI work.
Thanks again for taking the time to open the issue and the forum thread - much appreciated.
@TheGoldenPlatypus Welcome to the Ansible Forum.
Thanks for the quickly addressing those issues.
Thanks @TheGoldenPlatypus!
BTW Do you have any plans to do a new release? Or isn’t there anything worth releasing ATM?
yes, 1.1.0 is in flight and should ship soon. It brings our managed SaaS, RavenDB Cloud, under this collection as a new module set - ( 6 modules !) currently in review on #27