Skip to content

chore(release): bump chart to 0.5.2#76

Merged
Kiran01bm merged 1 commit intomainfrom
kiran01bm-webhook-chart-bump
May 6, 2026
Merged

chore(release): bump chart to 0.5.2#76
Kiran01bm merged 1 commit intomainfrom
kiran01bm-webhook-chart-bump

Conversation

@Kiran01bm
Copy link
Copy Markdown
Contributor

What

Bumps charts/version-guard/Chart.yaml:

  • version: 0.5.10.5.2
  • appVersion: "0.5.1""0.5.2"

Why

Cuts a fresh release containing PR #70 (Stage 3 NotifyEmitter — webhook-driven detector → emitter wire). Already verified end-to-end in staging (cash/utility) twice today using the SHA-tagged image 5afe8d7 (the merge SHA of PR #70)

Cutting v0.5.2 lets the production BPCI rollout pin a semver tag instead of a SHA, and re-aligns the chart's appVersion baseline with the released binary.

Release sequence (after merge)

  1. Tag from main: git tag -s v0.5.2 -m 'Release v0.5.2 (Stage 3 NotifyEmitter)' && git push origin v0.5.2.
  2. CI Docker & Helm workflow:
    • build-and-push publishes ghcr.io/block/version-guard:0.5.2 (also v0.5.2, 0.5, latest, sha-tagged).
    • Package and push Helm chart step gates on tag == Chart.yaml.version and pushes oci://ghcr.io/block/charts/version-guard:0.5.2.

Aligns chart version + appVersion with the upcoming v0.5.2 tag,
which ships PR #70 (Stage 3 NotifyEmitter wired detector → emitter).
The docker.yml release job gates the helm-chart push on
tag == Chart.yaml version, so both must match before tagging.
@Kiran01bm Kiran01bm requested a review from a team as a code owner May 6, 2026 22:07
@Kiran01bm Kiran01bm merged commit eb54b82 into main May 6, 2026
7 checks passed
@Kiran01bm Kiran01bm deleted the kiran01bm-webhook-chart-bump branch May 6, 2026 23:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants