readme: missing image tag in the container image replication diagram

Also update the GitHub Actions workflow badge.

Author: maelvls

README.md

@@ -1,4 +1,4 @@
-[![release-master](https://github.com/jetstack/jetstack-secure/actions/workflows/release-master.yml/badge.svg)](https://github.com/jetstack/jetstack-secure/actions/workflows/release-master.yml)
+[![tests](https://github.com/jetstack/jetstack-secure/actions/workflows/tests.yaml/badge.svg)](https://github.com/jetstack/jetstack-secure/actions/workflows/tests.yaml)
 [![Go Reference](https://pkg.go.dev/badge/github.com/jetstack/jetstack-secure.svg)](https://pkg.go.dev/github.com/jetstack/jetstack-secure)
 [![Go Report Card](https://goreportcard.com/badge/github.com/jetstack/jetstack-secure)](https://goreportcard.com/report/github.com/jetstack/jetstack-secure)
 
@@ -95,23 +95,22 @@ The release process is semi-automated.
 ### Step 1: Git Tag and GitHub Release
 
 1. Create a tag for the new release:
-    ```sh
-   export VERSION=v0.6.0-alpha.0
+   ```sh
+   export VERSION=v1.1.0
    git tag --annotate --message="Release ${VERSION}" "${VERSION}"
    git push origin "${VERSION}"
    ```
 2. A GitHub action will see the new tag and do the following:
-    - Build and publish the container image at `quay.io/jetstack/venafi-agent`,
-    - Build and publish the Helm chart at `oci://quay.io/jetstack/charts/venafi-kubernetes-agent`,
-    - Create a draft GitHub release,
-    - Upload the Helm chart tarball to the GitHub release.
+   - Build and publish the container image at `quay.io/jetstack/venafi-agent`,
+   - Build and publish the Helm chart at `oci://quay.io/jetstack/charts/venafi-kubernetes-agent`,
+   - Create a draft GitHub release,
+   - Upload the Helm chart tarball to the GitHub release.
 3. Navigate to the GitHub Releases page and select the draft release to edit.
-    2. Click on “Generate release notes” to automatically compile the changelog.
-    3. Review and refine the generated notes to ensure they’re clear and useful
-       for end users.
-    4. Remove any irrelevant entries, such as “update deps,” “update CI,”
-       “update docs,” or similar internal changes that do not impact user
-       functionality.
+   1. Click on “Generate release notes” to automatically compile the changelog.
+   2. Review and refine the generated notes to ensure they’re clear and useful
+      for end users.
+   3. Remove any irrelevant entries, such as “update deps,” “update CI,” “update
+      docs,” or similar internal changes that do not impact user functionality.
 4. Publish the release.
 5. Inform Michael McLoughlin of the new release so he can update the
    documentation at <https://docs.venafi.cloud/>.
@@ -158,8 +157,8 @@ The release process is semi-automated.
 > ```text
 > v1.1.0 (Git tag in the jetstack-secure repo)
 >  └── quay.io/jetstack/venafi-agent:v1.1.0 (GitHub Actions in the jetstack-secure repo)
->      ├── us.gcr.io/jetstack-secure-enterprise/venafi-agent (Enterprise Builds's GitHub Actions)
->      └── eu.gcr.io/jetstack-secure-enterprise/venafi-agent (Enterprise Builds's GitHub Actions)
+>      ├── us.gcr.io/jetstack-secure-enterprise/venafi-agent:v1.1.0 (Enterprise Builds's GitHub Actions)
+>      └── eu.gcr.io/jetstack-secure-enterprise/venafi-agent:v1.1.0 (Enterprise Builds's GitHub Actions)
 >          ├── registry.venafi.cloud/venafi-agent/venafi-agent:v1.1.0 (Harbor Replication)
 >          ├── private-registry.venafi.cloud/venafi-agent/venafi-agent:v1.1.0 (Harbor Replication)
 >          └── private-registry.venafi.eu/venafi-agent/venafi-agent:v1.1.0 (Harbor Replication)
@@ -212,5 +211,4 @@ The process is as follows:
 3. Create a pull request and wait for it to be approved.
 4. Merge the branch
 5. Manually trigger the Helm Chart workflow:
-[release_js-agent_chart.yaml](https://github.com/jetstack/enterprise-builds/actions/workflows/release_js-agent_chart.yaml).
-
+   [release_js-agent_chart.yaml](https://github.com/jetstack/enterprise-builds/actions/workflows/release_js-agent_chart.yaml).