Add 2.16 back to the tagger script #3461
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Even though 2.16 is EOL upstream there are still core releases happening so we should continue tagging docs to stay in sync.
oraNod
added
no_backport
felixfontein
approved these changes
Feb 5, 2026
gotmax23
approved these changes
Feb 5, 2026
Contributor
Author
|
Thanks for the reviews @felixfontein and @gotmax23 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Even though 2.16 is EOL upstream there are still core releases happening so we should continue tagging docs to stay in sync.
Relates: https://forum.ansible.com/t/tagging-ansible-documentation-for-2-16/45267