Skip to content

fix(ci): release revert commits so reverts reach the cluster#76

Merged
botantler-1[bot] merged 1 commit into
mainfrom
claude/ci-release-revert-commits
Jun 27, 2026
Merged

fix(ci): release revert commits so reverts reach the cluster#76
botantler-1[bot] merged 1 commit into
mainfrom
claude/ci-release-revert-commits

Conversation

@devantler

@devantler devantler commented Jun 27, 2026

Copy link
Copy Markdown
Contributor

Problem

The revert #75 (dropping the panic-on-create CodeRabbit ruleset) merged to main but never deployed. semantic-release reported:

[commit-analyzer] Analysis of 1 commits complete: no release
There are no relevant changes, so no new version is released.

The repo's .releaserc uses @semantic-release/commit-analyzer with default rules only (feat/fix/perf) — the revert type isn't covered. So no tag was cut, cd.yaml never re-published, and the github-config OCI artifact stayed at v1.8.0 (which still contains the broken ruleset). The failing OrganizationRuleset CR is therefore still on-cluster and un-pruned.

This is a latent bug: any revert(...) PR would silently fail to deploy.

Fix

Add a commit-analyzer releaseRule mapping revertpatch, so revert commits cut a release. Two effects:

  1. This fix: commit (a default release rule) cuts a patch now → cd.yaml republishes current main, which already has revert(rulesets): drop the provider-uncreatable CodeRabbit required-check ruleset #75's removal applied → Flux prunes the failing CR.
  2. Future revert(...) commits will release, so a revert always reaches the cluster.

Validated: .releaserc is valid JSON; revert→patch added without dropping the default feat/fix/perf rules.

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
    • Updated release automation so revert commits now trigger a patch release.
    • Release handling is now more consistent when changes are rolled back.

The revert #75 (dropping the panic-on-create CodeRabbit ruleset) merged to
main but semantic-release reported "no release": the default release rules
cover feat/fix/perf but not the `revert` type, so the deploy/ change was never
published — the github-config OCI artifact stayed at v1.8.0 (which still
contains the broken ruleset) and the failing OrganizationRuleset CR was never
pruned.

Add a commit-analyzer releaseRule mapping `revert` -> patch so revert commits
cut a release (and reach the cluster). This `fix:` commit itself triggers the
patch that republishes current main — with #75's removal already applied.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@botantler-1 botantler-1 Bot enabled auto-merge (squash) June 27, 2026 23:56
@coderabbitai

coderabbitai Bot commented Jun 27, 2026

Copy link
Copy Markdown

Review Change Stack

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: fcfbb876-24dd-44ba-b42e-990c646750fa

📥 Commits

Reviewing files that changed from the base of the PR and between ccf90b8 and a3b0954.

📒 Files selected for processing (1)
  • .releaserc

📝 Walkthrough

Walkthrough

.releaserc updates the @semantic-release/commit-analyzer plugin from a plain name string to a configured tuple, adding a releaseRules entry that maps commits of type revert to a patch release.

Changes

Semantic Release Configuration

Layer / File(s) Summary
revert commit release rule
.releaserc
@semantic-release/commit-analyzer is changed from an unconfigured string entry to a plugin tuple with releaseRules specifying that revert commits produce a patch release.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A revert once lost in the night,
Now earns a patch release with delight!
The rabbit hopped in, changed a rule,
No commit left out in the cold—how cool!
🐇✨

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/ci-release-revert-commits

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

@botantler-1 botantler-1 Bot merged commit 92b8ad5 into main Jun 27, 2026
8 of 9 checks passed
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