fix: release please chart sync

[jaronoff97]

No description provided.

[macroscopeapp]

🔴 Critical tero-edge/values.yaml:7

Setting image.tag to "@sha256:..." causes the rendered image reference to include a stray colon: ghcr.io/usetero/edge:@sha256:.... The template formats the image as {{ .Values.image.repository }}:{{ .Values.image.tag }}, so the @ prefix in the tag produces :@ instead of the valid digest separator @. Kubernetes rejects :@ in image references, so installs using the chart defaults fail to pull the tero-edge container. Set image.tag to "sha256:..." (without the leading @) so the template renders ghcr.io/usetero/edge:sha256:..., or update the template to handle digest references correctly.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file @charts/tero-edge/values.yaml around line 7:

Setting `image.tag` to `"@sha256:..."` causes the rendered image reference to include a stray colon: `ghcr.io/usetero/edge:@sha256:...`. The template formats the image as `{{ .Values.image.repository }}:{{ .Values.image.tag }}`, so the `@` prefix in the tag produces `:@` instead of the valid digest separator `@`. Kubernetes rejects `:@` in image references, so installs using the chart defaults fail to pull the `tero-edge` container. Set `image.tag` to `"sha256:..."` (without the leading `@`) so the template renders `ghcr.io/usetero/edge:sha256:...`, or update the template to handle digest references correctly.

[macroscopeapp]

Approvability

Verdict: Needs human review

1 blocking correctness issue found. An unresolved review comment identifies a critical bug: the image.tag value '@sha256:...' produces invalid Kubernetes image references that will fail to pull. This substantive issue warrants human review.

^{You can customize Macroscope's approvability policy. Learn more.}