Merge pull request #77 from github/release-policy-controller-v0.12.0-github10

Release policy-controller v0.12.0-github10

Author: codysoyland

Diff for: .github/workflows/test.yml

@@ -21,7 +21,7 @@ jobs:
 
       - uses: actions/setup-python@0b93645e9fea7318ecaed2b359559ac225c90a2b # v5.3.0
         with:
-          python-version: 3.7
+          python-version: '3.13'
 
       - name: Set up chart-testing
         uses: helm/chart-testing-action@e6669bcd63d7cb57cb4380c33043eebe5d111992 # v2.6.1

Diff for: 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.10.0-github9
+    oci://ghcr.io/github/artifact-attestations-helm-charts/policy-controller:v0.12.0-github10
 ```
 
 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.10.0-github9
+  --version v0.12.0-github10
 ```
 
 The `--atomic` flag will delete the installation if failure occurs.
@@ -91,8 +91,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.10.0-github9" -m "policy-controller-v0.10.0-github9"`
-1. Push the tag, ex: `git push origin "policy-controller-v0.10.0-github9"`
+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.12.0-github10" -m "policy-controller-v0.12.0-github10"`
+1. Push the tag, ex: `git push origin "policy-controller-v0.12.0-github10"`
 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 for: charts/policy-controller/Chart.yaml

@@ -8,8 +8,8 @@ sources:
 type: application
 
 name: policy-controller
-version: "v0.10.0-github9"
-appVersion: "v0.10.0-github9"
+version: "v0.12.0-github10"
+appVersion: "v0.12.0-github10"
 
 maintainers:
   - name: codysoyland

Diff for: 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.10.0-github9
-    version: sha256:50f166c1f19c6f910ba2426bdc153aeb033e41af77b835de931cb54f5e89d73c
+    # crane digest ghcr.io/github/policy-controller-webhook:v0.12.0-github10
+    version: sha256:9994eb53b3908a0a5735ad0fccbaea0ffca9e0818c6ad8761a70cf565338faf0
     pullPolicy: IfNotPresent
   env: {}
   extraArgs: {}