And here is the final release of the collection before renaming including redirects to the new collection name.
Do not use this release, if you want to stick with the old naming for now!
The renamed release will follow shortly.
Ladiiiieees and Gentlemen! 
We proudly present: The renamed Checkmk Ansible Collection! 
The version was bumped twice, as each step of the renaming posed a breaking change to users.
The transition is rather easy and you have several options. Check out this thread for more information on how to do it.
From this day forward, you will find the collection in this location: Ansible Galaxy
This is our first breaking release after the collection renaming. 
The breaking changes are:
- Aliases in module options that were deprecated for some time now, have been removed. This includes the following:
- host module:
host_name (use name instead)
- host_group module:
host_group_name (use name instead)
host_groups (use groups instead)
- rule module:
folder (use location instead)
- With Werk 15888 a change was introduced in Checkmk
2.2.0p7 that affects the way the folder module works in a breaking way. You will get a warning, if your Checkmk site is older than Checkmk 2.2.0p7 and an error if it is on 2.2.0p7 or newer, if the following applies: You used more than one of the following options in a single module call: attributes, update_attributes and remove_attributes. Moving forward, these are mutually exclusive and should not be used together.
Apart from these breaking changes a lot of work went into the CI infrastructure once again.
Phew, this was a big one! 
We worked for quite some time on finalizing Windows support for the agent role and here it is: Release 3.1.0 finally brings the long-awaited feature! 
Huge shout-out to @StefanM and our very own @Max! 
While Stefan did the heavy lifting of creating the initial pull request and creating most of the functionality, Max did the polishing and testing to make sure it meets our standards. 
There might still be issues, mind you, but we are positive, that most of you should get going without much struggle. And if something comes up, do let us know: File an issue on GitHub.
You might think, this is already big enough of an announcement, but hold on! We got one more!
@lars.getwan introduced a first lookup plugin, named version!
This allows you to easily look up the version of the Checkmk site you are talking to. For details on the usage, look at the plugin itself, or at playbooks/demo/lookup.yml. 
P.S.: Not a Friday-release! 
And here we are with a Wednesday release. I think that is a first. 
This one includes changes to the agent and server roles:
- We added support to download a folder-based agent, if no host-specific agent is available, before falling back to the GENERIC agent.
- We fixed a bug, where registration on remote sites would not work properly.
- We did some overall cleanup, overhaul, and bug fixing for the
agent role and a minor bug fix for the server role.
- And yet again, our CI got some love.
Overall you should not notice any problems, it is a rather small release. 
Attention: This release is now finally available on galaxy.ansible.com 
Thanks to the Galaxy developers for their support! 
The holiday season hit, and it took some time to get the next release ready.

Also, the Ansible Galaxy Team released a new codebase to galaxy.ansible.com. This took some looking-into on our end as well. If you experience issues there, read on here for more information: New Ansible Galaxy codebase, URLs to collections on Galaxy change · Issue #59 · ansible-collections/news-for-maintainers · GitHub or head for the Ansible Forum.
Now on to the release: It is packed again with new features. 
- @Max added a new module: The time period module.

- @lars.getwan added not one but four new lookup plugins for hosts and folders.

- @lars.getwan also created a version lookup utility, that can be used in your module code, and was already implemented in the
discovery module. 
- mueller-ma added firewall management support for the agent role.

- Additionally it is now possible to manage sites without specifying an admin password.
This can be useful for example, if you did not create the site with Ansible or you want to update a remote site and do not need the admin password. Be careful on site creation though, as without an admin_pw set during creation, a random password will be set. You can of course overwrite it later if you want.
- We also fixed an issue, where agent registration on a remote site would fail, if the host was just created.

Those are the noteworthy changes. The rest is documentation improvement and the usual cleanups. 
Now we are back on track with our releases, so we can proudly present:
The Checkmk Ansible Collection 3.4.0! 
This one is feature packed, once again:
- @hb9hnt added support for the agent in push mode (along with other modes of calling the agent, like SSH). This also fixes a bug, that would prevent the
agent role from properly working with agents in push mode.
Thanks, man! 
- S0obi made the logging of the roles better configurable, with focus on security.
Now the roles will by default not log tasks, that contain secrets. This can be disabled for trouleshooting, of course. 
- We added support for
omd config, which enabled fully automated deployments of Checkmk sites. 
- @StefanM added initial support for the Checkmk Managed Edition (CME).
Thanks, buddy! 
Apart from that, we have the typical built-related changes and minor fixes.
Also, this time the release to the new Galaxy worked flawlessly, so you can install the collection just as you are used to. 
Now, this is a big one. Seriously, we have two breaking changes and a new lookup plugin in this release. So strap in and let’s dive. 
Release 4.0.0 contains - among other things:
- Standardized variable names. For the up-to-date format see CHANGELOG.md → Style Guide → Roles and Playbooks. As most of these are used internally, most of you should not feel an impact. However, if you hook into any of the variables from e.g., your inventory or
extra-vars, double-check the variable names and align them with e.g., using the defaults/main.yml of the role you use.
- A reworked
agent role structure. We consider this a breaking change, as things might be broken for your use case, but we did our very best in testing. So the change should be seamless, and you should not see any changes in the behavior of the role. Nevertheless, we urge you to test the new release before running it in production (as you should always do).
- Support for Ansible
2.16.0.
- @Max was on fire this release and added not only the
bakery_lookup plugin, but also the following improvements. 
- Improved error handling for the lookup API.

- Proper support for the
redirect option in the activation module. This also gets rid of a nasty workaround in the agent role, where we had to wait for a fixed amount of time, to make sure the activation finished. Now the role can continue, once it gets confirmation of successful activation. 
If you need help, reach out here in the forum, using the ansible tag or if you found an issue, open a report on GitHub.
Just a quick bug fix release 4.0.1
Thanks to mueller-ma for finding this bug. 
4.3.0 has just been published. 
While there are a lot of changes that only affect our CI and testing, there are some things to point out nevertheless:
- @lars.getwan added the parameter
rule_id to the rule module, enabling targeting of specific ruled for modification or deletion. 
- @Max fixed a bug in the
user module, where an absent user was created in case the reset_password option was used. 
- @lars.getwan also fixed an issue with idempotency in the
folder module. 
- @sekania added a nifty feature, that enables usage of environment variables, inventory variables or variables put in
ansible.cfg by the lookup modules. This way you do not need to provide authentication on every lookup module call.
Refer to the module documentation for further details. 
- @sekania made the folder module even more powerful by enabling extended attribute management.
Refer to the module documentation for further details. 
- @sekania (three times in a row, impressive dude!
) fixed an issue with setting parents on hosts and folders, where a single parent provided as a string would be chopped into single characters. 
That concludes today’s release. Maybe an issue, that has been bugging you as well was fixed, maybe you love the new functionality. One way or another, I hope you like this release. 
It was certainly a piece of work. 
We just discovered a small but impactful bug in the last release:
The rule module would create all rules, no matter the provided conditions without these conditions. 
This has been fixed with bugfix release 4.3.1. 
Shout out to Mik3yZ for noticing and fixing this issue so quickly! 