# \#ansible-documentatio

**URL:** https://forum.ansible.com/tag/ansible-documentatio/457.md

[Latest](https://forum.ansible.com/latest.md) · [Categories](https://forum.ansible.com/categories.md) · [Tags](https://forum.ansible.com/tags.md)

---

## [Tagging Ansible documentation for 2.16](https://forum.ansible.com/t/tagging-ansible-documentation-for-2-16/45267)

<div class="topic-metadata">

**Author:** [@oranod](https://forum.ansible.com/u/oranod)\
**Replies:** 20\
**Last updated:** [March 1, 2026, 2:55pm UTC](https://forum.ansible.com/t/tagging-ansible-documentation-for-2-16/45267 "2026-03-01T14:55:59Z")

</div>

Hi everyone, The ansible-core project is still releasing 2.16 versions for downstream purposes even though 2.16 is EOL upstream. I removed 2.16 from the tagger script in the ansible/ansible-documentation repo back in No…

---

## [Ansible Release Process update : new Github Action workflow to create Porting\_Guide PR](https://forum.ansible.com/t/ansible-release-process-update-new-github-action-workflow-to-create-porting-guide-pr/44020)

<div class="topic-metadata">

**Author:** [@anwesha](https://forum.ansible.com/u/anwesha)\
**Replies:** 0\
**Last updated:** [July 23, 2025, 1:03pm UTC](https://forum.ansible.com/t/ansible-release-process-update-new-github-action-workflow-to-create-porting-guide-pr/44020 "2025-07-23T13:03:41Z")

</div>

For the Ansible automated release process, we now have a new GitHub action in the ansible-documentation repository to create the Porting Guide pull request needed for Ansible Package Release. This helps the release mana…