Release v1.1.6

? Release v1.1.6

Version Bumps Applied:

• Major: false
• Minor: false
• Patch: true

Triggered by: PR #14 - release: merge dev into main
Merged by: @notchjpl

Changes in this PR

Release PR: merges dev into main.

Labelled release + patch so Auto Release on Main Merge cuts a patch release on merge, which in turn triggers the production build.

What this carries

• BUILD_TIME build-arg + buildtime step in the build workflows. aws_prod_release.yml on main is the file a release build actually uses (the tag points at a main commit), so prod images only start reporting a build time once this is merged.
• paths-ignore: ['argo/**'] on the dev build trigger — now the only guard against the rebuild loop, since [skip ci] has been removed from the Argo CD Image Updater commit template.
• Whatever else is already on dev for this app. Please review the file list before merging; some repos carry unreleased application work.

Why the label test matters

Until today, dev -> main release PRs were being silently dropped: Image Updater stamped [skip ci] on its digest write-back commit, that commit became the tip of dev, and GitHub applies [skip ci] to pull_request events too — keyed on the PR HEAD commit. No workflow run, no check suite, no release. Twelve releases had to be cut by hand.

[skip ci] has since been removed from the template (infra-terraform k8-mgmt/argo.tf) and replaced by the path filter, and every repo's dev HEAD has been verified clean of it. Merging this PR with the labels attached is the end-to-end confirmation that Auto Release fires on its own again.

---

This release was automatically created by the Auto Release workflow

What's Changed

• argo dev config sync by @LinaBell in #11
• chore: expose COMMIT_HASH and BUILD_TIME on the health endpoint by @notchjpl in #12
• release: merge dev into main by @notchjpl in #14

Full Changelog: v1.1.5...v1.1.6