-
Notifications
You must be signed in to change notification settings - Fork 396
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
[stable-6] Lock sanity test versions based on what we were testing when 7.0.0 was released #2000
[stable-6] Lock sanity test versions based on what we were testing when 7.0.0 was released #2000
Conversation
6a60b20
to
496cdc5
Compare
…en 7.0.0 was released
496cdc5
to
080a56b
Compare
Build succeeded. ❌ ansible-galaxy-importer FAILURE in 5m 10s (non-voting) |
c3144a1
to
e051ac1
Compare
e051ac1
to
b19e7e7
Compare
Build succeeded. ❌ ansible-galaxy-importer FAILURE in 4m 53s (non-voting) |
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 3m 43s (non-voting) |
Build succeeded (gate pipeline). ❌ ansible-galaxy-importer FAILURE in 5m 06s (non-voting) |
Pull request merge failed: Resource not accessible by integration, You may need to manually rebase your PR and retry. |
SUMMARY
Now that
stable-6
is primarily security-/bug- fixes only, lock the Ansible/Python versions of the Ansible sanity tests that we run. Explicitly excludes running against the milestone/devel versions of the tests since they're a moving target. While we should be applying these fixes tomain
/stable-7
, many of the fixes are primarily cosmetic in nature and don't warrant backporting all the way intostable-6
and beyond.ISSUE TYPE
COMPONENT NAME
.github/workflows/sanity.yml
ADDITIONAL INFORMATION