feat(lcm): default retag tag to latest, resolving version from the image

[santos1709]

The retag workflow derived the major version by string-splitting the tag input, so a latest input would have produced Mlatest-<cluster>. This PR resolves the concrete version from the image itself instead: the build stamps LABEL bricks_version from the BRICKS_VERSION build-arg, so crane config | jq .config.Labels.bricks_version is authoritative and independent of mutable tag names.

With that in place, default the tag input to latest.

Summary by CodeRabbit

• Bug Fixes
  • Improved stable image retagging for explicit versions and the latest tag.
  • Added validation to ensure latest matches the resolved version before retagging.
  • Updated workflow summaries to report the actual resolved version.

[coderabbitai]

📝 Walkthrough

Walkthrough

The stable retag workflow now accepts explicit versions or latest, resolves versions from image labels, verifies matching digests for latest, retags major cluster aliases, and reports the resolved versions in the workflow summary.

Changes

Stable retag workflow

Layer / File(s)	Summary
Input and version resolution .github/workflows/lcm-stable-retag.yaml	The workflow accepts explicit version tags or latest; image bricks_version labels are validated as semantic versions.
Retagging and summary output .github/workflows/lcm-stable-retag.yaml	latest digest consistency is checked, M<major>-<cluster> tags are updated, and the summary reports resolved versions.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Sequence Diagram(s)

sequenceDiagram
  participant GitHubActions
  participant ContainerRegistry
  participant ImageManifest
  GitHubActions->>ContainerRegistry: Resolve requested image
  ContainerRegistry->>ImageManifest: Read bricks_version label
  ImageManifest-->>GitHubActions: Return resolved X.Y.Z version
  GitHubActions->>ContainerRegistry: Compare latest and resolved digests when requested
  GitHubActions->>ContainerRegistry: Retag M<major>-<cluster> aliases
  GitHubActions-->>GitHubActions: Write resolved workflow summary

Loading

Possibly related PRs

• gooddata/gooddata-ruby#2087: Both modify the stable retag workflow’s tag-selection and retagging logic.
• gooddata/gooddata-ruby#2088: Both add resolved-version and digest-consistency handling to LCM workflows.

Poem

A bunny found a tag named “latest,”
Then checked its digest—nice and stately.
The version label led the way,
Major cluster tags now hop and stay.
The summary blooms with facts so bright,
Retagging safely through the night. 🐇

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main workflow change: defaulting the retag target to latest and resolving the version from the image.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/lcm-stable-retag.yaml:
- Around line 111-122: Update the version-resolution flow around the TAG/latest
branch so every TAG value, including explicit rollback inputs, is passed through
resolve_version using the bricks_version input; only the latest path should
retain the stable-tag digest comparison. Derive major and src from the resolved
concrete version, and ensure summaries use that same resolved value.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 3c6e9815-0af1-481f-a885-923a35be7b63

📥 Commits

Reviewing files that changed from the base of the PR and between 97a77ca and ba68bde.

📒 Files selected for processing (1)

• .github/workflows/lcm-stable-retag.yaml