Prepare release 0.7.0.

changelogs/fragments/agent_role.yml

@@ -3,6 +3,7 @@
 minor_changes:
   - Agent role - Host attributes can be fully customized now.
   - Agent role - Check for agent updater and controller binaries. Skip registration if respective binary is missing.
+  - Agent role - Label role. This enables skipping or running tasks exclusively. See the README for a detailed list.
 
 bugfixes:
   - Agent role - Support CFE properly.

changelogs/fragments/bugfix_activation_module.yml

@@ -2,6 +2,7 @@
 
 bugfixes:
   - Activation module - Fix waiting for activation completion (#103).
+  - Activation module - Fix possible race condition. (#123).
 
 # known_issues:
 #   - This release is still in development and a heavy work in progress.

changelogs/fragments/release_summary.yml

@@ -0,0 +1,3 @@
+# https://docs.ansible.com/ansible/latest/community/development_process.html#changelogs-how-to
+
+release_summary: "Lots of love for the agent role!"

changelogs/fragments/server_role.yml

@@ -0,0 +1,48 @@
+# https://docs.ansible.com/ansible/latest/community/development_process.html#changelogs-how-to
+
+minor_changes:
+  - Server role - Label role. This enables skipping or running tasks exclusively. See the README for a detailed list.
+
+# known_issues:
+#   - This release is still in development and a heavy work in progress.
+#   - Discovery module is not feature complete yet.
+#   - Downtime module is not fully idempotent yet. This affects service downtimes and deletions.
+
+## Line Format
+# When writing a changelog entry, use the following format:
+
+# - scope - description starting with a lowercase letter and ending with a period at the very end. Multiple sentences are allowed (https://github.com/reference/to/an/issue or, if there is no issue, reference to a pull request itself).
+
+# The scope is usually a module or plugin name or group of modules or plugins, for example, lookup plugins. While module names can (and should) be mentioned directly (foo_module), plugin names should always be followed by the type (foo inventory plugin).
+
+# For changes that are not really scoped (for example, which affect a whole collection), use the following format:
+
+# - Description starting with an uppercase letter and ending with a dot at the very end. Multiple sentences are allowed (https://github.com/reference/to/an/issue or, if there is no issue, reference to a pull request itself).
+
+
+## Possible keys:
+
+# breaking_changes
+
+#     Changes that break existing playbooks or roles. This includes any change to existing behavior that forces users to update tasks. Displayed in both the changelogs and the Porting Guides.
+# major_changes
+
+#     Major changes to Ansible itself. Generally does not include module or plugin changes. Displayed in both the changelogs and the Porting Guides.
+# minor_changes
+
+#     Minor changes to Ansible, modules, or plugins. This includes new features, new parameters added to modules, or behavior changes to existing parameters.
+# deprecated_features
+
+#     Features that have been deprecated and are scheduled for removal in a future release. Displayed in both the changelogs and the Porting Guides.
+# removed_features
+
+#     Features that were previously deprecated and are now removed. Displayed in both the changelogs and the Porting Guides.
+# security_fixes
+
+#     Fixes that address CVEs or resolve security concerns. Include links to CVE information.
+# bugfixes
+
+#     Fixes that resolve issues.
+# known_issues
+
+#     Known issues that are currently not fixed or will not be fixed.

galaxy.yml

@@ -9,7 +9,7 @@ namespace: tribe29
 name: checkmk
 
 # The version of the collection. Must be compatible with semantic versioning
-version: 0.6.0
+version: 0.7.0
 
 # The path to the Markdown (.md) readme file. This path is relative to the root of the collection
 readme: README.md

requirements.yml

@@ -1,4 +1,4 @@
 ---
 collections:
   - name: tribe29.checkmk
-    version: 0.6.0
+    version: 0.7.0