|
| 1 | +--- |
| 2 | + |
| 3 | +# You can copy its contents into a .yaml file with a unique filename. A common |
| 4 | +# convention is to prefix the filename with the number of an issue or pull/merge |
| 5 | +# request. This file uses the .txt extension to prevent antsibull-changelog from |
| 6 | +# parsing it. |
| 7 | +# |
| 8 | +# Remove any sections that are not applicable to your changelog fragment. |
| 9 | +# |
| 10 | +# For more information, see the official documentation on |
| 11 | +# "Creating Changelog Fragments": |
| 12 | +# https://docs.ansible.com/ansible/latest/community/development_process.html#creating-changelog-fragments |
| 13 | +# |
| 14 | +# The file format is YAML, but the content of the values is typically written |
| 15 | +# in reStructuredText (not Markdown). |
| 16 | + |
| 17 | +breaking_changes: |
| 18 | + - This section should only appear in major releases (MAJOR.0.0), according to semantic versioning. |
| 19 | + - It should include notes and `Links <https://example.com/>`__ to help existing users migrate. |
| 20 | + - Examples follow. |
| 21 | + - Dropped support for Ansible Core 2.15. Please update to at least Ansible Core 2.16 or continue using a previous version of this collection. |
| 22 | + - The ``foo_api`` module no longer accepts the ``password_plain`` option. Use ``password_secure`` instead. If you previously supplied passwords via ``password_plain``, consider changing them. |
| 23 | + - | |
| 24 | + This is a multiline string using YAML's block scalar syntax. |
| 25 | + It makes "quoting" 'easier'. |
| 26 | + |
| 27 | +major_changes: |
| 28 | + - This section should only appear in major (MAJOR.0.0) (but are also technically allowed in minor (MAJOR.MINOR.0) releases), according to semantic versioning. |
| 29 | + - It should describe high-level changes or new features. |
| 30 | + - Examples follow. |
| 31 | + - Added support for a new ``acme_dns`` module, allowing DNS-based certificate challenges with additional providers. |
| 32 | + - The ``http_request`` module now supports custom headers and authentication tokens. |
| 33 | + |
| 34 | +minor_changes: |
| 35 | + - This section can appear in all major (MAJOR.MINOR.PATCH) or minor (MAJOR.MINOR.0) releases, but not in patch (MAJOR.MINOR.PATCH) releases. |
| 36 | + - A typical minor change includes adding a new module, plugin, or option. |
| 37 | + - Examples follow. |
| 38 | + - ``foo`` - The module can now perform additional operations based on user-defined parameters. |
| 39 | + - ``baz lookup`` - Now supports retrieving data from Baz databases. |
| 40 | + - Optimized task execution performance by reducing unnecessary API calls. |
| 41 | + |
| 42 | +deprecated_features: |
| 43 | + - This section should list features planned for removal in future major (MAJOR.0.0) releases. |
| 44 | + - Examples follow. |
| 45 | + - ``foo`` - The ``bar`` option has been deprecated. Use the ``username`` option instead. |
| 46 | + - ``send_request`` - The ``quic`` option has been deprecated. Use the ``protocol`` option instead. |
| 47 | + |
| 48 | +removed_features: |
| 49 | + - This section can appear in major (MAJOR.0.0) or minor (MAJOR.MINOR.0) releases. |
| 50 | + - Typically used when the change is non-breaking from the collection's perspective (e.g. backend removal). |
| 51 | + - Examples follow. |
| 52 | + - ``foo`` - The ``baz`` option has been removed. The feature it controlled is no longer supported on target platforms. |
| 53 | + |
| 54 | +security_fixes: |
| 55 | + - This section can appear in all releases. |
| 56 | + - Examples follow. |
| 57 | + - ``foo_api`` - The module unintentionally exposed passwords in plaintext to multiple servers when using the ``password_plain`` option. |
| 58 | + |
| 59 | +bugfixes: |
| 60 | + - This section can appear in all releases. |
| 61 | + - Examples follow. |
| 62 | + - ``post`` - The module incorrectly sent PUT requests instead of POST requests. |
| 63 | + - ``get`` - The module no longer crashes when receiving invalid JSON data. |
| 64 | + |
| 65 | +known_issues: |
| 66 | + - This section should describe known issues that are acknowledged but will not be fixed at this time. |
| 67 | + |
| 68 | +trivial: |
| 69 | + - This section will not be shown in the final changelog. |
| 70 | + - Useful when a changelog fragment is required for every pull request, even for minor or internal changes. |
| 71 | + - Intended for changes that do not affect user-facing functionality, such as updates to tests or internal refactoring. |
0 commit comments