-
Notifications
You must be signed in to change notification settings - Fork 670
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
commit 7fa5f76e0333a97476b5204487f183efb5e3d467 breaks backward compatibility of the ansible-lint github action #3928
Comments
This is happening for us as well , is their a workaround available? |
Facing same issue . any solution would be highly appreciated |
my interim fix is to use the latest aka. main instead of a pinned version/tag |
it's weird if I use the specific version: name: ansible-lint
on: [pull_request]
jobs:
build:
name: Ansible Lint # Naming the build is important to use it as a status check
runs-on: ubuntu-latest
steps:
- name: Checkout Code
uses: actions/checkout@v2
- name: Run ansible-lint
uses: ansible/ansible-lint@v6.20.0 GitHub actions still
Shouldn't it be |
I think this was the fix |
So, anything before |
Fixed as part of #3929 |
can confirm the fix is working ... at least the workflow will not fail due to the missing requirement file ...
|
good to hear ... the future is saved ... 👍 |
Summary
while 2 days ago calling
ansible/ansible-lint@v6.22.0
(see https://github.com/zerwes/ansible-role-checkmkagent/actions/runs/7083656545) worked without any problems, after the commit 7fa5f76 calling a tagget version of the action will fail due to the file renaming with a error (see https://github.com/Rosa-Luxemburgstiftung-Berlin/ansible-opnsense/actions/runs/7097243220/job/19317040697)error:
Issue Type
OS / ENVIRONMENT
github action
STEPS TO REPRODUCE
create a github action with
Desired Behavior
agile paradigm should not break backward compatibility ...
Actual Behavior
see https://github.com/Rosa-Luxemburgstiftung-Berlin/ansible-opnsense/actions/runs/7097243220/job/19317040697
The text was updated successfully, but these errors were encountered: