-
Notifications
You must be signed in to change notification settings - Fork 199
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
Ansible 2.10.17 is still not supported #979
Comments
Use v0.3.x for Ansible 2.10+ |
but this version is still not released :( |
Released, 0.3.3 is the latest version https://pypi.org/project/mitogen/ |
ok , missed information. |
I think you should probably fix the documentation which pops up as the first result in google then: By fixing I basically mean updating the version on a regular basis there. It may look self-evident for others, but it's actually misleading, because you automatically think that that is the latest version. I saw that mitogen was still actively developed, and I got the error that I couldn't use a higher version than 2.9 (eol in May 2022). I'm using 2.14.3 now. I'm still not sure how I'm supposed to install mitogen and integrate it with ansible though :) |
Take mitogen from master, patch version requirement, and it works with 2.14. More or less, as it was before (some bleeding corner-cases, but you get used to them pretty quickly). |
Yes, thank you, I was eventually able to use the latest stable version of mitogen and downgrade ansible to 2.10 (latest from ubuntu 22.04). I don't need the latest ansible version. |
In case it helps others: I was able to use mitogen 0.3.3 with ansible-core 2.12.10. |
@moreati I'm new to Mitogen so I may not be aware of how the release cycles work. The current Ansible version seems to be 8, with core at 2.15. When is Mitogen expected to support the current release? |
ERROR! Your Ansible version (2.10.17) is too recent. The most recent version
supported by Mitogen for Ansible is (2, 9).x. Please check the Mitogen
release notes to see if a new version is available, otherwise
subscribe to the corresponding GitHub issue to be notified when
support becomes available.
The text was updated successfully, but these errors were encountered: