You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Utils - With Checkmk 2.2.0p3 the activation introduces a breaking change, which we need to handle. As a workaround we added the 'If-Match' header to all API requests.
3
+
4
+
known_issues:
5
+
- Utils - All API calls send the 'If-Match' header. This is a workaround and will be fixed in a future release.
- Integration tests - A bug was fixed, where the integration tests did not use the correct Checkmk version.
11
+
12
+
#
13
+
## Line Format:
14
+
#
15
+
16
+
# When writing a changelog entry, use the following format:
17
+
18
+
# - scope - description starting with a uppercase letter and ending with a period at the very end. Multiple sentences are allowed.
19
+
20
+
# 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).
21
+
22
+
# For changes that are not really scoped (for example, which affect a whole collection), use the following format:
23
+
24
+
# - Description starting with an uppercase letter and ending with a dot at the very end. Multiple sentences are allowed.
25
+
26
+
27
+
#
28
+
## Possible keys:
29
+
#
30
+
# release_summary
31
+
# Adds a single line release summary to the changelog.
32
+
33
+
# breaking_changes
34
+
# 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.
35
+
36
+
# major_changes
37
+
# Major changes to Ansible itself. Generally does not include module or plugin changes. Displayed in both the changelogs and the Porting Guides.
38
+
39
+
# minor_changes
40
+
# Minor changes to Ansible, modules, or plugins. This includes new features, new parameters added to modules, or behavior changes to existing parameters.
41
+
42
+
# deprecated_features
43
+
# Features that have been deprecated and are scheduled for removal in a future release. Displayed in both the changelogs and the Porting Guides.
44
+
45
+
# removed_features
46
+
# Features that were previously deprecated and are now removed. Displayed in both the changelogs and the Porting Guides.
47
+
48
+
# security_fixes
49
+
# Fixes that address CVEs or resolve security concerns. Include links to CVE information.
50
+
51
+
# bugfixes
52
+
# Fixes that resolve issues.
53
+
54
+
# known_issues
55
+
# Known issues that are currently not fixed or will not be fixed.
0 commit comments