We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Seems this detail is in the changelogs - https://github.com/ansible-community/ansible-build-data/blob/main/4/CHANGELOG-v4.rst#id867
But that's a bit buried. Would be great if we could put it at the top of the porting guide as well - https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_5.html#ansible-5-porting-guide Maybe just add a heading 'ansible-core 2.12 Porting Guide' and put all that detail under that new header?
The text was updated successfully, but these errors were encountered:
A simple fix is to mention it similarly as in the case where two consecutive Ansible major releases have the same ansible-core major release (https://github.com/ansible-community/antsibull/blob/1f621e65c55ebb4b2fdab710f1bda5fa9c4f276a/src/antsibull/build_changelog.py#L653). I've implemented that in #397.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Seems this detail is in the changelogs - https://github.com/ansible-community/ansible-build-data/blob/main/4/CHANGELOG-v4.rst#id867
But that's a bit buried. Would be great if we could put it at the top of the porting guide as well - https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_5.html#ansible-5-porting-guide
Maybe just add a heading 'ansible-core 2.12 Porting Guide' and put all that detail under that new header?
The text was updated successfully, but these errors were encountered: