Skip to content

docs: add release process and update integration template to v0.6.1#137

Open
gnaponie wants to merge 1 commit into
mainfrom
docs/release-process
Open

docs: add release process and update integration template to v0.6.1#137
gnaponie wants to merge 1 commit into
mainfrom
docs/release-process

Conversation

@gnaponie

@gnaponie gnaponie commented May 4, 2026

Copy link
Copy Markdown
Collaborator

Document the full release process in README. Also regenerate integrations/gitlab-ci/claudio.yml (was stale at v0.5.0-dev).

Summary by CodeRabbit

  • Documentation

    • Clarified the step-by-step release process in the README.
  • Chores

    • Updated internal CI/CD configuration to reference the latest tooling version.

Document the full release process in README. Also regenerate
integrations/gitlab-ci/claudio.yml (was stale at v0.5.0-dev).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Signed-off-by: Giulia Naponiello <gnaponie@redhat.com>
@coderabbitai

coderabbitai Bot commented May 4, 2026

Copy link
Copy Markdown

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 554909ad-6a27-4afc-bb11-4c5ec4d6fd4d

📥 Commits

Reviewing files that changed from the base of the PR and between 1a272b3 and 25e0cf3.

📒 Files selected for processing (2)
  • README.md
  • integrations/gitlab-ci/claudio.yml

📝 Walkthrough

Walkthrough

Documentation of the release process is added to the README, which includes steps for bumping the version, regenerating CI templates, and tagging releases. Concurrently, the claudio container image reference in the GitLab CI template is updated from v0.5.0-dev to v0.6.1.

Changes

Release Documentation and Version Bump

Layer / File(s) Summary
Documentation
README.md
New "Releasing" section outlines the step-by-step process: bump VERSION in Makefile, run make integrations-update to regenerate GitLab CI templates, create a release PR, and tag/push the merge commit. Also documents post-merge CI behavior and clarifies patch releases follow the same workflow.
Configuration
integrations/gitlab-ci/claudio.yml
CLAUDIO_IMAGE default updated from quay.io/aipcc-cicd/claudio:v0.5.0-dev to quay.io/aipcc-cicd/claudio:v0.6.1, reflecting the updated container version for the .claudio job template.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A version hops forward with care,
Release notes and templates laid bare,
From dev to release, the process takes flight,
CI rebuilds the image just right,
Each tag marks a milestone so fair! 🏷️

🚥 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 accurately summarizes both main changes: adding release process documentation and updating the integration template version to v0.6.1.
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 docs/release-process

Review rate limit: 9/10 reviews remaining, refill in 6 minutes.

Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant