Skip to content
This repository has been archived by the owner on Aug 2, 2023. It is now read-only.

Upgrade action to use ansible-lint v5 #48

Closed
wants to merge 2 commits into from

Conversation

ssbarnea
Copy link
Member

@ssbarnea ssbarnea commented Feb 23, 2021

Update action to make use of currently supported version of ansible-lint, as old ones are no longer supported.

Fixes: #45

@ssbarnea
Copy link
Member Author

@webknjaz Apparently this did not trigger any jobs either.

@webknjaz
Copy link
Member

Why would it?

@ssbarnea
Copy link
Member Author

I was expecting some testing of the proposed change. What if I mistakenly put some junk in it?

@frankenstein91
Copy link

@ssbarnea
Copy link
Member Author

ssbarnea commented Apr 25, 2021

Since this PR was originally created 5 more releases of ansible-lint happened. I updated it but now I wonder if this is prone to always be outdated.

I was already contacted by multiple users confused about the fact that the GHA for the linter is outdated. If is a little bit behind is not a big deal, but clearly not like this. Even galaxy server switched to use v5, i think without pinning.

@hugovk
Copy link

hugovk commented Jan 13, 2022

@GElkayam
Copy link

Hi @webknjaz,
any plans to move this forward? is the project still alive?

@ssbarnea
Copy link
Member Author

I was asking the same myself, especially as now this action can make use of the pre-built creator-ee container.

@ssbarnea ssbarnea closed this Mar 21, 2022
@ssbarnea ssbarnea deleted the master branch March 21, 2022 08:40
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ansible-lint v5 now requires ansible?
5 participants