-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update dependency community.crypto to v2.15.1 - autoclosed #145
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/community.crypto-2.x
branch
from
November 2, 2022 13:22
bf0c261
to
a40dac4
Compare
renovate
bot
changed the title
Update dependency community.crypto to v2.7.1
Update dependency community.crypto to v2.8.0
Nov 2, 2022
renovate
bot
changed the title
Update dependency community.crypto to v2.8.0
Update dependency community.crypto to v2.8.1
Nov 6, 2022
renovate
bot
force-pushed
the
renovate/community.crypto-2.x
branch
from
November 6, 2022 21:42
a40dac4
to
a0769e4
Compare
renovate
bot
force-pushed
the
renovate/community.crypto-2.x
branch
from
November 27, 2022 19:03
a0769e4
to
42428ac
Compare
renovate
bot
changed the title
Update dependency community.crypto to v2.8.1
Update dependency community.crypto to v2.9.0
Nov 27, 2022
renovate
bot
force-pushed
the
renovate/community.crypto-2.x
branch
from
January 2, 2023 22:19
42428ac
to
b56faf1
Compare
renovate
bot
changed the title
Update dependency community.crypto to v2.9.0
Update dependency community.crypto to v2.10.0
Jan 2, 2023
renovate
bot
force-pushed
the
renovate/community.crypto-2.x
branch
from
February 23, 2023 11:06
b56faf1
to
8740c5a
Compare
renovate
bot
changed the title
Update dependency community.crypto to v2.10.0
Update dependency community.crypto to v2.11.0
Feb 23, 2023
renovate
bot
changed the title
Update dependency community.crypto to v2.11.0
Update dependency community.crypto to v2.11.1
Mar 24, 2023
renovate
bot
force-pushed
the
renovate/community.crypto-2.x
branch
from
March 24, 2023 08:05
8740c5a
to
12e9072
Compare
renovate
bot
force-pushed
the
renovate/community.crypto-2.x
branch
from
April 16, 2023 20:49
12e9072
to
73d0e17
Compare
renovate
bot
changed the title
Update dependency community.crypto to v2.11.1
Update dependency community.crypto to v2.12.0
Apr 16, 2023
renovate
bot
force-pushed
the
renovate/community.crypto-2.x
branch
from
May 28, 2023 09:24
73d0e17
to
5941054
Compare
renovate
bot
changed the title
Update dependency community.crypto to v2.12.0
Update dependency community.crypto to v2.13.1
May 28, 2023
renovate
bot
changed the title
Update dependency community.crypto to v2.13.1
Update dependency community.crypto to v2.14.0
Jun 15, 2023
renovate
bot
force-pushed
the
renovate/community.crypto-2.x
branch
from
June 15, 2023 14:32
5941054
to
87b3331
Compare
renovate
bot
changed the title
Update dependency community.crypto to v2.14.0
Update dependency community.crypto to v2.14.1
Jun 27, 2023
renovate
bot
force-pushed
the
renovate/community.crypto-2.x
branch
from
June 27, 2023 19:21
87b3331
to
ed8b762
Compare
renovate
bot
changed the title
Update dependency community.crypto to v2.14.1
Update dependency community.crypto to v2.15.0
Aug 12, 2023
renovate
bot
force-pushed
the
renovate/community.crypto-2.x
branch
from
August 12, 2023 19:04
ed8b762
to
ab07d7b
Compare
renovate
bot
force-pushed
the
renovate/community.crypto-2.x
branch
from
August 22, 2023 07:09
ab07d7b
to
1b0b5ac
Compare
renovate
bot
changed the title
Update dependency community.crypto to v2.15.0
Update dependency community.crypto to v2.15.1
Aug 22, 2023
renovate
bot
changed the title
Update dependency community.crypto to v2.15.1
Update dependency community.crypto to v2.15.1 - autoclosed
Oct 7, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.7.0
->2.15.1
Release Notes
ansible-collections/community.crypto (community.crypto)
v2.15.1
Compare Source
=======
Release Summary
Bugfix release.
Bugfixes
type
(https://github.com/ansible-collections/community.crypto/issues/651, https://github.com/ansible-collections/community.crypto/pull/652).v2.15.0
Compare Source
=======
Release Summary
Bugfix and feature release.
Minor Changes
Deprecated Features
false
of theasn1_base64
option is deprecated and will change totrue
in community.crypto 3.0.0 (https://github.com/ansible-collections/community.crypto/pull/600).Bugfixes
ssh
andssh-keygen
in some cases (https://github.com/ansible-collections/community.crypto/issues/645, https://github.com/ansible-collections/community.crypto/pull/646).New Plugins
Filter
v2.14.1
Compare Source
=======
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
-----BEGIN
(https://github.com/ansible-collections/community.crypto/issues/627, https://github.com/ansible-collections/community.crypto/pull/628).Known Issues
v2.14.0
Compare Source
=======
Release Summary
Feature release.
Minor Changes
no challenge
for thechallenge
option. This is needed for ACME servers where validation is done without challenges (https://github.com/ansible-collections/community.crypto/issues/613, https://github.com/ansible-collections/community.crypto/pull/615).path
parameter (https://github.com/ansible-collections/community.crypto/issues/603).v2.13.1
Compare Source
=======
Release Summary
Bugfix release.
Bugfixes
python3-pyOpenSSL
package on CentOS and RHEL (https://github.com/ansible-collections/community.crypto/pull/606).python3-pyOpenSSL
package for Rocky Linux 9+ (https://github.com/ansible-collections/community.crypto/pull/606).v2.13.0
Compare Source
=======
Release Summary
Bugfix and maintenance release.
Minor Changes
crl_mode
option has been added to replace the existingmode
option (https://github.com/ansible-collections/community.crypto/issues/596).Deprecated Features
mode
option is deprecated; usecrl_mode
instead. Themode
option will change its meaning in community.crypto 3.0.0, and will refer to the CRL file's mode instead (https://github.com/ansible-collections/community.crypto/issues/596).Bugfixes
regenerate=fail
without an existing key, contradicting the documentation (https://github.com/ansible-collections/community.crypto/pull/598).AnsibleModule
is now validating themode
parameter's values (https://github.com/ansible-collections/community.crypto/issues/596).v2.12.0
Compare Source
=======
Release Summary
Feature release.
Minor Changes
asn1_base64
option to control whether the ASN.1 included in theextensions
return value is binary data or Base64 encoded (https://github.com/ansible-collections/community.crypto/pull/592).v2.11.1
Compare Source
=======
Release Summary
Maintenance release with improved documentation.
v2.11.0
Compare Source
=======
Release Summary
Feature and bugfix release.
Minor Changes
ciphers
option for custom cipher selection (https://github.com/ansible-collections/community.crypto/pull/571).Bugfixes
python3-pyOpenSSL
dependency resolution on RHEL 9+ / CentOS Stream 9+ platforms (https://github.com/ansible-collections/community.crypto/pull/575).Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.