versions 2.3.1 and 2.3.2

[dsexton18]

Hello team,

I noticed that the changelog.rst lists versions 2.3.1 and 2.3.2, but there are no corresponding Git tags or releases in the repository. As a result, only 2.3.0 is available on Ansible Galaxy

[dsexton18]

Hello team,

I noticed that changelog.rst already documents versions 2.3.1 and 2.3.2, but there are no corresponding Git tags or GitHub releases. The latest tag in the repo is 2.3.0, so on Ansible Galaxy only 2.3.0 is available.

I reviewed the commit history after 2.3.0 and found the following candidate SHAs that appear to align with what the changelog describes:

2.3.1 (bugfix release) — possible tag at be6ab30

2.3.2 (feature + fix release) — possible tag at d377606 (or possibly at the latest commit 766d8be)

If these align with what you intended in the changelog, perhaps the following commands could be used to push the missing tags:

git tag -a 2.3.1 be6ab30 -m "Release 2.3.1 per changelog" git tag -a 2.3.2 d377606 -m "Release 2.3.2 per changelog" git push origin 2.3.1 git push origin 2.3.2

If these SHAs aren’t correct (or if the changelog corresponds differently), would you mind confirming which commit SHAs you used for 2.3.1 and 2.3.2, so the tags/releases can be added appropriately?

Thanks very much for the work on this — making the versions/tags match the changelog would help a lot for downstream users.