Repository navigation
Releases
v0.35.0
Published by .github/workflows/release.yml from 4bbd9ff.
Operator image digest:
sha256:25a854a231292f7d268cfa92f7291d1b8c8e1cd1e939022c547552866ede926e
This workflow does not commit it, and the reason that step is a person's
and not this job's is in the CI design's §5.
Put it where the deployment is described -- a HelmRelease's values, a
kustomize patch -- and not into charts/spawnery/values.yaml's
image.digest, which this text told people to do until v0.1.2. A digest
cannot usefully live in the chart: it comes from skopeo copy --digestfile
and so does not exist until after the tag is published, which makes the
value in any released chart the previous release's. Worse, setting it
silences internal/rbacaudit's TestTheOperatorImageIsNotAMutableTag, which
returns early when a digest is present and therefore stops checking the
tag beside it.
Install
helm install spawnery oci://ghcr.io/spawnery/charts/spawnery \
--version 0.35.0 \
--namespace spawnery-system --create-namespacev0.34.0
Published by .github/workflows/release.yml from 9b49827.
Operator image digest:
sha256:2c9a2199268e73f117021e5ec8f8c8fc89fa7d112d8c660d3225e8fc62591c96
This workflow does not commit it, and the reason that step is a person's
and not this job's is in the CI design's §5.
Put it where the deployment is described -- a HelmRelease's values, a
kustomize patch -- and not into charts/spawnery/values.yaml's
image.digest, which this text told people to do until v0.1.2. A digest
cannot usefully live in the chart: it comes from skopeo copy --digestfile
and so does not exist until after the tag is published, which makes the
value in any released chart the previous release's. Worse, setting it
silences internal/rbacaudit's TestTheOperatorImageIsNotAMutableTag, which
returns early when a digest is present and therefore stops checking the
tag beside it.
Install
helm install spawnery oci://ghcr.io/spawnery/charts/spawnery \
--version 0.34.0 \
--namespace spawnery-system --create-namespacev0.33.0
Published by .github/workflows/release.yml from 66232af.
Operator image digest:
sha256:7239722cee83cdd20150f780357bf2d28addcd8c43ce5e8e497a14e40e996895
This workflow does not commit it, and the reason that step is a person's
and not this job's is in the CI design's §5.
Put it where the deployment is described -- a HelmRelease's values, a
kustomize patch -- and not into charts/spawnery/values.yaml's
image.digest, which this text told people to do until v0.1.2. A digest
cannot usefully live in the chart: it comes from skopeo copy --digestfile
and so does not exist until after the tag is published, which makes the
value in any released chart the previous release's. Worse, setting it
silences internal/rbacaudit's TestTheOperatorImageIsNotAMutableTag, which
returns early when a digest is present and therefore stops checking the
tag beside it.
Install
helm install spawnery oci://ghcr.io/spawnery/charts/spawnery \
--version 0.33.0 \
--namespace spawnery-system --create-namespacev0.32.0
Published by .github/workflows/release.yml from cf8594e.
Operator image digest:
sha256:95d70ac09c098f20c5dc1b94b799a7d86987bf9bcd93f952a86a5b53cac2bcac
This workflow does not commit it, and the reason that step is a person's
and not this job's is in the CI design's §5.
Put it where the deployment is described -- a HelmRelease's values, a
kustomize patch -- and not into charts/spawnery/values.yaml's
image.digest, which this text told people to do until v0.1.2. A digest
cannot usefully live in the chart: it comes from skopeo copy --digestfile
and so does not exist until after the tag is published, which makes the
value in any released chart the previous release's. Worse, setting it
silences internal/rbacaudit's TestTheOperatorImageIsNotAMutableTag, which
returns early when a digest is present and therefore stops checking the
tag beside it.
Install
helm install spawnery oci://ghcr.io/spawnery/charts/spawnery \
--version 0.32.0 \
--namespace spawnery-system --create-namespacev0.31.0
Published by .github/workflows/release.yml from 6dfa7da.
Operator image digest:
sha256:78851611ba9edabf932d29d4dcd5e25402ec8c342ee27cfdf8add6b0c32212f8
This workflow does not commit it, and the reason that step is a person's
and not this job's is in the CI design's §5.
Put it where the deployment is described -- a HelmRelease's values, a
kustomize patch -- and not into charts/spawnery/values.yaml's
image.digest, which this text told people to do until v0.1.2. A digest
cannot usefully live in the chart: it comes from skopeo copy --digestfile
and so does not exist until after the tag is published, which makes the
value in any released chart the previous release's. Worse, setting it
silences internal/rbacaudit's TestTheOperatorImageIsNotAMutableTag, which
returns early when a digest is present and therefore stops checking the
tag beside it.
Install
helm install spawnery oci://ghcr.io/spawnery/charts/spawnery \
--version 0.31.0 \
--namespace spawnery-system --create-namespacev0.30.1
Published by .github/workflows/release.yml from 7197e6b.
No new operator image on this tag: it was already published at the version
flake.nix names, and charts/spawnery/values.yaml's image.digest is
unchanged.
Install
helm install spawnery oci://ghcr.io/spawnery/charts/spawnery \
--version 0.30.0 \
--namespace spawnery-system --create-namespaceThat chart is not new on this tag -- charts/ has not moved since the
previous one, so version 0.30.0 is the artefact an earlier release
already pushed, and it is the right one to install.
v0.30.0
Published by .github/workflows/release.yml from 541863f.
Operator image digest:
sha256:16552434434ea9d169678577eae9b8a64d3004aedaaaa2759f427b279b7c98b0
This workflow does not commit it, and the reason that step is a person's
and not this job's is in the CI design's §5.
Put it where the deployment is described -- a HelmRelease's values, a
kustomize patch -- and not into charts/spawnery/values.yaml's
image.digest, which this text told people to do until v0.1.2. A digest
cannot usefully live in the chart: it comes from skopeo copy --digestfile
and so does not exist until after the tag is published, which makes the
value in any released chart the previous release's. Worse, setting it
silences internal/rbacaudit's TestTheOperatorImageIsNotAMutableTag, which
returns early when a digest is present and therefore stops checking the
tag beside it.
Install
helm install spawnery oci://ghcr.io/spawnery/charts/spawnery \
--version 0.30.0 \
--namespace spawnery-system --create-namespacev0.29.0
Published by .github/workflows/release.yml from baeffbe.
Operator image digest:
sha256:0abd60d34782ba9a2faa025670b26a0eae4ff3dd5f705ad55ca0f2d83a619095
This workflow does not commit it, and the reason that step is a person's
and not this job's is in the CI design's §5.
Put it where the deployment is described -- a HelmRelease's values, a
kustomize patch -- and not into charts/spawnery/values.yaml's
image.digest, which this text told people to do until v0.1.2. A digest
cannot usefully live in the chart: it comes from skopeo copy --digestfile
and so does not exist until after the tag is published, which makes the
value in any released chart the previous release's. Worse, setting it
silences internal/rbacaudit's TestTheOperatorImageIsNotAMutableTag, which
returns early when a digest is present and therefore stops checking the
tag beside it.
Install
helm install spawnery oci://ghcr.io/spawnery/charts/spawnery \
--version 0.29.0 \
--namespace spawnery-system --create-namespacev0.28.1
Published by .github/workflows/release.yml from 9739bd8.
No new operator image on this tag: it was already published at the version
flake.nix names, and charts/spawnery/values.yaml's image.digest is
unchanged.
Install
helm install spawnery oci://ghcr.io/spawnery/charts/spawnery \
--version 0.28.0 \
--namespace spawnery-system --create-namespaceThat chart is not new on this tag -- charts/ has not moved since the
previous one, so version 0.28.0 is the artefact an earlier release
already pushed, and it is the right one to install.
v0.28.0
Published by .github/workflows/release.yml from 49122b6.
Operator image digest:
sha256:10cdaf66464da7748af41cbf37c5c7427ba4c84b8d755b0578073f8a7618b188
This workflow does not commit it, and the reason that step is a person's
and not this job's is in the CI design's §5.
Put it where the deployment is described -- a HelmRelease's values, a
kustomize patch -- and not into charts/spawnery/values.yaml's
image.digest, which this text told people to do until v0.1.2. A digest
cannot usefully live in the chart: it comes from skopeo copy --digestfile
and so does not exist until after the tag is published, which makes the
value in any released chart the previous release's. Worse, setting it
silences internal/rbacaudit's TestTheOperatorImageIsNotAMutableTag, which
returns early when a digest is present and therefore stops checking the
tag beside it.
Install
helm install spawnery oci://ghcr.io/spawnery/charts/spawnery \
--version 0.28.0 \
--namespace spawnery-system --create-namespace