From 0bc25158099b4d7cbeb7d736c5fd2200fc482ce0 Mon Sep 17 00:00:00 2001 From: Andres Hernandez Date: Mon, 11 Nov 2024 09:51:37 -0600 Subject: [PATCH] README: Fix version publishing list (#245) Fix Markdown list --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 55cc491..e6b9ab3 100644 --- a/README.md +++ b/README.md @@ -179,18 +179,18 @@ where the `IMAGE_FORMAT` environment variable is the full reference to your cont Releases are automatically built and pushed to Ansible Galaxy for any new tag. Before tagging a release, make sure to do the following: - 1. Update the version in the following places: +1. Update the version in the following places: * a. The `version` in `galaxy.yml` * b. This README's `requirements.yml` example * c. The `DOWNSTREAM_VERSION` in `ci/downstream.sh` * d. The `VERSION` in `Makefile` * e. The version in `requirements.yml` - 2. Update the CHANGELOG: +2. Update the CHANGELOG: * 1. Make sure you have [`antsibull-changelog`](https://pypi.org/project/antsibull-changelog/) installed. * 2. Make sure there are fragments for all known changes in `changelogs/fragments`. * 3. Run `antsibull-changelog release`. - 3. Commit the changes and create a PR with the changes. Wait for tests to pass, then merge it once they have. - 4. Tag the version in Git and push to GitHub. +3. Commit the changes and create a PR with the changes. Wait for tests to pass, then merge it once they have. +4. Tag the version in Git and push to GitHub. After the version is published, verify it exists on the [OKD Collection Galaxy page](https://galaxy.ansible.com/community/okd).