-
Notifications
You must be signed in to change notification settings - Fork 12
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
Bump up the lower bound on ansible-core
#196
Merged
jsf9k
merged 3 commits into
develop
from
improvement/add-a-lower-bound-pin-for-ansible-core
Nov 20, 2024
Merged
Bump up the lower bound on ansible-core
#196
jsf9k
merged 3 commits into
develop
from
improvement/add-a-lower-bound-pin-for-ansible-core
Nov 20, 2024
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
This is being done because the pip-audit pre-commit hook identifies a vulnerability in ansible-core version 2.16.13. Note that this requires that we bump up ansible to version 10 since all versions of ansible 9 have a dependency on ~=2.16.X.
jsf9k
added
improvement
This issue or pull request will add or improve functionality, maintainability, or ease of use
dependencies
Pull requests that update a dependency file
security
This issue or pull request addresses a security issue
labels
Nov 8, 2024
dv4harr10
approved these changes
Nov 8, 2024
This was referenced Nov 8, 2024
dav3r
approved these changes
Nov 12, 2024
mcdonnnj
reviewed
Nov 13, 2024
The pin of ansible-core was originally put in place because the pip-audit pre-commit hook identifies a vulnerability in ansible-core 2.16.13. Normally we would pin ansible-core to >2.16.13, but in the spirit of the earlier, optional pin of ansible>=10 we pin ansible-core to >=2.17. This effectively also pins ansible to >=10. Co-authored-by: Nick M <[email protected]>
5 tasks
mcdonnnj
reviewed
Nov 20, 2024
This adds even more evidence for why it is a good idea to go ahead and upgrade ansible and ansible-core, in addition to the vulnerability that pip-audit turned up. Co-authored-by: Nick M <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
dependencies
Pull requests that update a dependency file
improvement
This issue or pull request will add or improve functionality, maintainability, or ease of use
security
This issue or pull request addresses a security issue
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.
🗣 Description
This pull request bumps up the lower bound on the
ansible-core
Python package.See also cisagov/skeleton-ansible-role#209 and the commits cisagov/skeleton-packer@26a8baf and cisagov/skeleton-packer@19fbaf3 in cisagov/skeleton-packer#376.
💭 Motivation and context
This is being done because the
pip-audit
pre-commit
hook identifies a vulnerability inansible-core
version 2.16.13. Note that this requires that we bump up the version ofansible
to version 10 since all versions ofansible
9 have a dependency onansible-core~=2.16.X
.🧪 Testing
All automated tests pass.
✅ Pre-approval checklist