ci: write image tag to global.image.tag#17
Conversation
The applications repo now sets the image once under `global.image` (generic chart 1.7.0 fallbacks); the bump writes the single canonical path `.global.image.tag` in default.yaml instead of per-alias keys. Merge AFTER appwrite-labs/assets-applications#29 — until then per-alias writes still override global, so deploys stay correct either way. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Greptile SummaryThis PR updates the staging deployment workflow to write the image tag to
Confidence Score: 5/5Both the The two-line change is internally consistent — the No files require special attention. Important Files Changed
Reviews (2): Last reviewed commit: "Update staging.yml" | Re-trigger Greptile |
ChiragAgg5k
left a comment
There was a problem hiding this comment.
I cannot approve this as-is: the workflow now writes to ${{ env.ENVIRONMENT }}/${{ env.PROJECT }}/default.yaml, but the commit step still runs git add ${{ env.ENVIRONMENT }}/${{ env.PROJECT }}/fra1.yaml. That means the modified default.yaml file will not be staged, so the deploy job can report "No changes to commit" and skip pushing the updated tag. Please update the git add path to default.yaml to match the yq target.
The applications repo moves
imagetoglobal.image(generic chart 1.7.0 — see appwrite-labs/helm-charts#17); this updates the tag-bump automation to write the single canonical path.global.image.tagindefault.yaml.Merge order: land appwrite-labs/assets-applications#29 first. Until then, an old-style per-alias write still overrides
global, so deploys stay correct in either interim state (a stale per-alias tag key would just need removing).🤖 Generated with Claude Code