ci: persist authenticator/gateway appVersions + bump on manual rebuild - #1890
Merged
cyberantonz merged 3 commits intoJul 24, 2026
Merged
Conversation
The release pipeline pinned backend image versions via each service's subchart appVersion, but two gaps meant those versions never reached the stand: - publish-chart bumped authenticator/gateway/helm/Chart.yaml in the work tree (so the packaged chart was momentarily correct) but the commit step staged only analytics/identity/frontend. The bumps were never persisted, so the next release re-anchored to main (where both are still "0.1.0") and republished the umbrella with those services pinned to a non-existent 0.1.0 tag — reverting them on deploy. Stage authenticator and gateway too. (main currently shows identity=<build tag> but authenticator=gateway="0.1.0", confirming the drift.) - The per-service bump and bump-descriptors only fired on push. A manual workflow_dispatch full rebuild built every image but bumped nothing, so the freshly built tags were never pinned. Bump every service on a full rebuild (mirroring the build jobs' own trigger) and allow bump-descriptors to run on workflow_dispatch. After merge, a manual full rebuild re-pins every service consistently. Refs constructorfabric#1583 Signed-off-by: Anton Zelenov <antonz@constructor.tech>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe build workflow now permits descriptor bumps during manual dispatches, updates all backend subchart ChangesChart versioning workflow
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related issues
Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
cyberantonz
enabled auto-merge (squash)
July 24, 2026 02:50
mitasovr
approved these changes
Jul 24, 2026
mozhaev-dev
approved these changes
Jul 24, 2026
cyberantonz
added a commit
that referenced
this pull request
Jul 24, 2026
…ld) (#1894) #1890 added the backend subchart appVersion bump + persistence, but only in publish-chart. On a manual full rebuild (or any run where a connector also changed), bump-descriptors commits the connector bumps and publish-chart is deferred to the re-triggered run via its `committed != 'true'` gate — so the backend bump never ran and only connectors got new versions (observed on run 30071800363). - Extract the per-service appVersion bump into scripts/bump-service-appversions.sh, shared by publish-chart and bump-descriptors so both pin the same set identically. - bump-descriptors now also bumps + stages the backend subchart Chart.yaml files in its (re-triggering) commit. The follow-up push run then rebuilds those backends and publish-chart persists their tags — backends end pinned to an image that exists, connectors keep their bumps. Refs #1583 Signed-off-by: Anton Zelenov <antonz@constructor.tech>
3 tasks
cyberantonz
pushed a commit
to cyberantonz/insight
that referenced
this pull request
Jul 27, 2026
The bump-descriptors and "commit version bumps back to main" steps in build-images.yml staged a hardcoded list of backend subchart Chart.yaml files that never included src/backend/services/identity-resolution/helm/Chart.yaml (bump-service- appversions.sh does bump it correctly in the run's workspace — it's just never git-added, so the bump is silently discarded). constructorfabric#1890 fixed the identical gap for authenticator/gateway three days earlier; identity-resolution landed as a subchart the next day (constructorfabric#1918) and missed the same two lists. Because the umbrella chart's appVersion computation already reads this file (line ~1345, unaffected), the chart still "worked" on any release that also rebuilt identity-resolution in the same CI run — the bump landed in the workspace and got packaged, just never persisted to main. The first release afterward that didn't touch identity-resolution's source packaged whatever was last committed: the original "0.0.0-dev" placeholder, which isn't a real GHCR tag. On dev (where identityResolution.deploy is now true post-cutover), that rendered an unpullable image, the migrate initContainer got stuck in ImagePullBackOff, and the umbrella upgrade failed on its progress deadline and auto-rolled back — repeatedly, since nothing fixed the root cause between attempts. One-time restore: set appVersion back to the last known-good tag (2026.07.25.07.16-a122f77 — verified currently running on dev) so the next release packages an existing image instead of the placeholder. Signed-off-by: Sergei Mozhaev <mozhaev.dev@gmail.com>
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Backend service image versions are pinned via each service's subchart
appVersion(set inpublish-chart). Two gaps meant those bumps never reached the deployed stand:Bumps not persisted (the revert bug).
publish-chartbumpsauthenticator/gatewayhelm/Chart.yamlin the working tree, so the packaged chart artifact is momentarily correct — but the finalgit addin "Commit version bumps back to main" staged onlyanalytics/identity/frontend. So the authenticator/gateway bumps were never committed. The next release re-anchors tomain(where both are still"0.1.0") and republishes the umbrella with those services pinned to a non-existent0.1.0tag → deploy reverts them.Evidence on
mainright now:identitysubchartappVersion= a real build tag ✓ (it's in thegit addlist)authenticator="0.1.0"✗ (never persisted, despite many builds)gateway="0.1.0"✗Manual full rebuild bumped nothing. The per-service bump gates on
changes.<svc> == 'true'andbump-descriptorsrequiredevent_name == 'push'. Aworkflow_dispatchfull rebuild built every image but pinned none of the fresh tags.Fix
authenticator+gatewaysubchartChart.yamlin the release commit so their bumps persist.appVersionon a manual full rebuild (workflow_dispatch+ emptyfrontend_tag), mirroring the build jobs' own trigger.bump-descriptorsto run onworkflow_dispatch(connectors already fan out via--all).bump-descriptors'sdiscover-images.outputs.anygate is intentionally left as-is: it only patches connector descriptors, so it's correctly skipped when no connector changed — the backend path is the subchart-appVersion mechanism above.After merge
Trigger one manual full rebuild (Actions → Build & Push Container Images → Run workflow, no
frontend_tag) to re-pin every service consistently from a single build.Refs #1583
🤖 Generated with Claude Code
Summary by CodeRabbit
New Features
Bug Fixes