Use release tag for Docker image tag

[lukaskratzel]

Pass the GitHub release tag explicitly to the reusable Docker build workflow so release builds publish images with the exact Git tag instead of relying on fallback tag derivation.

Summary by CodeRabbit

• Chores
  • Improved container image tagging to align with release versions for better version consistency.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 2125caea-4a9e-40dc-bc69-56ccca9f1d88

📥 Commits

Reviewing files that changed from the base of the PR and between 375ef32 and 0075c52.

📒 Files selected for processing (1)

• .github/workflows/build.yml

---

📝 Walkthrough

Walkthrough

The workflow now dynamically selects container image tags based on trigger type: GitHub Release events use release tag names, manual workflow dispatches use provided input values, and other events use empty strings as default fallback values.

Changes

Release Event Tagging

Layer / File(s)	Summary
Release tag conditional in build jobs .github/workflows/build.yml	The image-tag parameter in three build-and-push jobs (operator, service, conversion-webhook) is updated to conditionally use github.event.release.tag_name when triggered by a release event, fall back to inputs.image_tag for manual workflow runs, and default to empty string otherwise.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• EduIDE/EduIDE-Cloud#58: Also modifies .github/workflows/build.yml workflow image tagging logic for build-and-push jobs, involving release vs. main branch tag selection.

Suggested labels

ready to merge

Suggested reviewers

• CodeByNikolas

Poem

🐰 A rabbit hops through release events so fine,
Tags from GitHub flow like carrot wine,
Workflows dance in conditional delight,
Build and push the code day and night,
Automation springs when releases take flight! 🚀

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Use release tag for Docker image tag' directly describes the main change: using GitHub release tags for Docker image tagging in the build workflow.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/release-image-tag

---

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 and usage tips.}

[Copilot]

Pull request overview

Updates the CI build workflow so that on a GitHub release event, the release's Git tag name is passed as the Docker image-tag input to the reusable Docker build workflow. Previously the image-tag was only set for workflow_dispatch and defaulted to empty otherwise, leaving release builds to rely on the reusable workflow's fallback tag derivation. The change applies identically to the three image build jobs (operator, service, conversion-webhook).

Changes:

• For release events, set image-tag to github.event.release.tag_name.
• Preserve existing workflow_dispatch behavior using inputs.image_tag.
• Apply the same expression consistently across operator, service, and conversion-webhook jobs.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.