ansible==10.0.0 breaks the workflows
#115
Labels
problem
Something isn't working
Comments
|
Rather than pinning a specific version, shall we specify that we use a major version and install that - e.g. |
|
Ansible 9 will have minor and bugfix releases until Novemeber 2024 And worth looking at the Ansible 10 roadmap to see if any of the breaking changes are relevant to us. |
|
Having discussed this with @HChughtai, think I'm going to change it to |
paddyroddy
added a commit
that referenced
this issue
Jun 5, 2024
In the process of fixing things around #115, we want to use different options in the composite action related to UCL-MIRSG/.github#121 & UCL-MIRSG/.github#122. This would mean we'd need to set extra options in the reusable workflow, which will get confusing. By removing the reusable workflow, this will simplify things greatly. This will lead to more verbose code, but better in the long-term.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Short Description
Not entirely sure what the breakage is, but probably related to #110. This has been fixed for now with #114 - but ideally we don't want to pin
ansiblelong-term.Evidence/Steps to Reproduce
Run
moleculewithansible>=10.0.0Acceptance Criteria/Expected Behaviour
No response
Details
No response
Resolution
No response
The text was updated successfully, but these errors were encountered: