From 3b145ef84ffc7c449cff7aa5885f8dfaed92fc6f Mon Sep 17 00:00:00 2001
From: Cody Soyland <codysoyland@github.com>
Date: Tue, 9 Jul 2024 15:47:01 -0400
Subject: [PATCH] Release policy-controller v0.10.0-github5

Signed-off-by: Cody Soyland <codysoyland@github.com>
---
 README.md                            | 8 ++++----
 charts/policy-controller/Chart.yaml  | 4 ++--
 charts/policy-controller/values.yaml | 4 ++--
 3 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/README.md b/README.md
index f474d16..d9a0712 100644
--- a/README.md
+++ b/README.md
@@ -12,7 +12,7 @@ the [Attest Build Provenance Action](https://github.com/github/artifact-attestat
 You can verify these releases using the [`gh` CLI](https://cli.github.com/manual/gh_attestation_verify):
 ```bash
 gh attestation verify --owner github \
-    oci://ghcr.io/github/artifact-attestations-helm-charts/policy-controller:v0.9.0-github4
+    oci://ghcr.io/github/artifact-attestations-helm-charts/policy-controller:v0.10.0-github5
 ```
 
 For more information, see [our documentation](https://docs.github.com/en/actions/security-guides/using-artifact-attestations-to-establish-provenance-for-builds) on using artifact attestations to establish build provenance and [our blog post](https://github.blog/2024-05-02-introducing-artifact-attestations-now-in-public-beta/) introducing Artifact Attestations.
@@ -26,7 +26,7 @@ You will need to install two charts. First, install the Sigstore policy controll
 helm install policy-controller --atomic \
   --create-namespace --namespace artifact-attestations \
   oci://ghcr.io/github/artifact-attestations-helm-charts/policy-controller \
-  --version v0.9.0-github4
+  --version v0.10.0-github5
 ```
 
 The `--atomic` flag will delete the installation if failure occurs.
@@ -89,8 +89,8 @@ please file an [issue](https://github.com/github/artifact-attestations-helm-char
 When you are ready to cut a new release for a given Helm chart
 
 1. Update the chart's `AppVersion` and `Version` to the appropriate values
-1. Create a new tag prefixed with the targeted chart name in the format <my-chart-name>-v0.1.2, ex: `git tag -s "policy-controller-v0.9.0-github4" -m "policy-controller-v0.9.0-github4"`
-1. Push the tag, ex: `git push origin "policy-controller-v0.9.0-github4"`
+1. Create a new tag prefixed with the targeted chart name in the format <my-chart-name>-v0.1.2, ex: `git tag -s "policy-controller-v0.10.0-github5" -m "policy-controller-v0.10.0-github5"`
+1. Push the tag, ex: `git push origin "policy-controller-v0.10.0-github5"`
 1. The [release workflow](.github/workflows/release.yml) will be triggered if
 the chart's tag format is included in the list of tags that trigger the workflow.
 The tag must follow the format `<my-chart-name>-v<semantic-version>`
diff --git a/charts/policy-controller/Chart.yaml b/charts/policy-controller/Chart.yaml
index b949cde..0a0f648 100644
--- a/charts/policy-controller/Chart.yaml
+++ b/charts/policy-controller/Chart.yaml
@@ -8,8 +8,8 @@ sources:
 type: application
 
 name: policy-controller
-version: "v0.9.0-github4"
-appVersion: "v0.9.0-github4"
+version: "v0.10.0-github5"
+appVersion: "v0.10.0-github5"
 
 maintainers:
   - name: codysoyland
diff --git a/charts/policy-controller/values.yaml b/charts/policy-controller/values.yaml
index bf7de34..3281dbe 100644
--- a/charts/policy-controller/values.yaml
+++ b/charts/policy-controller/values.yaml
@@ -16,8 +16,8 @@ webhook:
   name: webhook
   image:
     repository: ghcr.io/github/policy-controller-webhook
-    # crane digest ghcr.io/github/policy-controller-webhook:v0.9.0-github4
-    version: sha256:239a2b43aeeaef2b9f16b41c931060fc35f2cb0f27ed28fbf1c7df938f6ef1f5
+    # crane digest ghcr.io/github/policy-controller-webhook:v0.10.0-github5
+    version: sha256:048a124b6f287a742956006730844ff5553d00bc12ec99ed1793480d7fbec814
     pullPolicy: IfNotPresent
   env: {}
   extraArgs: {}