Pin molecule-plugins and jmespath in default python-dependencies - #45
Merged
Conversation
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
0x46616c6b
marked this pull request as ready for review
July 26, 2026 08:38
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Pins the two remaining unversioned entries in the default
python-dependenciesof the integration workflow so the molecule toolchain is fully deterministic, matching the already-pinnedansible-coreandmolecule:molecule-plugins[docker]→==26.7.15jmespath→==1.0.1molecule-plugins26.7.15 introduced the docker driver JSON schema that broke consuming repos and required the fix in #44. Pinning it (andjmespath) prevents a future upstream release from silently changing behaviour in every consuming role again, and makes CI runs reproducible.🤖 Generated with Claude Code