Skip to content

Commit

Permalink
Release 2.14.1.
Browse files Browse the repository at this point in the history
  • Loading branch information
felixfontein committed Jun 27, 2023
1 parent 83af72a commit 6c72734
Show file tree
Hide file tree
Showing 5 changed files with 67 additions and 18 deletions.
28 changes: 28 additions & 0 deletions CHANGELOG.rst
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,34 @@ Community Crypto Release Notes
.. contents:: Topics


v2.14.1
=======

Release Summary
---------------

Bugfix and maintenance release with updated documentation.

From this version on, community.crypto is using the new `Ansible semantic markup
<https://docs.ansible.com/ansible/devel/dev_guide/developing_modules_documenting.html#semantic-markup-within-module-documentation>`__
in its documentation. If you look at documentation with the ansible-doc CLI tool
from ansible-core before 2.15, please note that it does not render the markup
correctly. You should be still able to read it in most cases, but you need
ansible-core 2.15 or later to see it as it is intended. Alternatively you can
look at `the devel docsite <https://docs.ansible.com/ansible/devel/collections/community/crypto/>`__
for the rendered HTML version of the documentation of the latest release.


Bugfixes
--------

- Fix PEM detection/identification to also accept random other lines before the line starting with ``-----BEGIN`` (https://github.com/ansible-collections/community.crypto/issues/627, https://github.com/ansible-collections/community.crypto/pull/628).

Known Issues
------------

- Ansible markup will show up in raw form on ansible-doc text output for ansible-core before 2.15. If you have trouble deciphering the documentation markup, please upgrade to ansible-core 2.15 (or newer), or read the HTML documentation on https://docs.ansible.com/ansible/devel/collections/community/crypto/.

v2.14.0
=======

Expand Down
39 changes: 39 additions & 0 deletions changelogs/changelog.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -858,6 +858,45 @@ releases:
- 617-acme_certificate-parallel.yml
- 622-der-format-support.yml
release_date: '2023-06-15'
2.14.1:
changes:
bugfixes:
- Fix PEM detection/identification to also accept random other lines before
the line starting with ``-----BEGIN`` (https://github.com/ansible-collections/community.crypto/issues/627,
https://github.com/ansible-collections/community.crypto/pull/628).
known_issues:
- Ansible markup will show up in raw form on ansible-doc text output for ansible-core
before 2.15. If you have trouble deciphering the documentation markup, please
upgrade to ansible-core 2.15 (or newer), or read the HTML documentation on
https://docs.ansible.com/ansible/devel/collections/community/crypto/.
release_summary: 'Bugfix and maintenance release with updated documentation.
From this version on, community.crypto is using the new `Ansible semantic
markup
<https://docs.ansible.com/ansible/devel/dev_guide/developing_modules_documenting.html#semantic-markup-within-module-documentation>`__
in its documentation. If you look at documentation with the ansible-doc CLI
tool
from ansible-core before 2.15, please note that it does not render the markup
correctly. You should be still able to read it in most cases, but you need
ansible-core 2.15 or later to see it as it is intended. Alternatively you
can
look at `the devel docsite <https://docs.ansible.com/ansible/devel/collections/community/crypto/>`__
for the rendered HTML version of the documentation of the latest release.
'
fragments:
- 2.14.1.yml
- 628-pem-detection.yml
- semantic-markup.yml
release_date: '2023-06-27'
2.2.0:
changes:
bugfixes:
Expand Down
11 changes: 0 additions & 11 deletions changelogs/fragments/2.14.1.yml

This file was deleted.

2 changes: 0 additions & 2 deletions changelogs/fragments/628-pem-detection.yml

This file was deleted.

5 changes: 0 additions & 5 deletions changelogs/fragments/semantic-markup.yml

This file was deleted.

0 comments on commit 6c72734

Please sign in to comment.