feat: add release workflow for tagged builds

[rophy]

Summary

• Add GitHub Actions workflow triggered on v* tags
• Builds release image via Dockerfile.release and pushes to ghcr.io/rophy/openlogreplicator:<tag>
• Uses GITHUB_TOKEN for GHCR auth (no extra secrets needed)

Test plan

• Merge PR, push v1.9.0.1 tag, verify workflow runs and image appears in GHCR

Summary by CodeRabbit

• Chores
  • Added automated container image building and publishing workflow for version releases.

[coderabbitai]

Warning

Rate limit exceeded

@rophy has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 37 minutes and 17 seconds before requesting another review.

To continue reviewing without waiting, purchase usage credits in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 03249b31-aff3-4c41-a8a5-cb849a0bbf82

📥 Commits

Reviewing files that changed from the base of the PR and between e66847d and 3103896.

📒 Files selected for processing (1)

• .github/workflows/release.yaml

📝 Walkthrough

Walkthrough

A new GitHub Actions workflow is added that automatically builds and publishes a Docker container image to GitHub Container Registry whenever a version tag matching v* is pushed. The workflow configures Docker Buildx, authenticates to the registry, builds from Dockerfile.release with environment-specific build arguments, and pushes the resulting image.

Changes

Cohort / File(s)	Summary
Release Workflow Configuration .github/workflows/release.yaml	New GitHub Actions workflow that triggers on version tags (v*), sets up Docker Buildx, authenticates to GitHub Container Registry, and builds/pushes release container image with OLR_VERSION and feature flags (Oracle, Kafka, Protobuf, Prometheus) enabled.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A new workflow hops into place,
Docker images run at full pace,
Tags trigger the build with care,
Container releases float through the air! 📦✨

🚥 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 clearly and accurately summarizes the main change: adding a GitHub Actions release workflow triggered on version tags.
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 feat/release-workflow

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

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.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/workflows/release.yaml:
- Around line 11-13: The workflow's job-level permissions only set packages:
write which can leave contents scoped to none and cause actions/checkout@v4 to
fail; update the permissions block in .github/workflows/release.yaml to include
contents: read alongside packages: write so the GITHUB_TOKEN has repository
contents read access required by actions/checkout@v4.

🪄 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: cb2ff861-32c7-4f69-b54e-36aa9f1d7c2d

📥 Commits

Reviewing files that changed from the base of the PR and between 21955ba and e66847d.

📒 Files selected for processing (1)

• .github/workflows/release.yaml

[rophy]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[rophy]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.