ci: restore .releaserc.json (unblocks main's CI/CD release)#128
Merged
Conversation
bf522b4 ("chore: clean slate for total refactor") removed the project- local semantic-release config. The reusable release workflow at jacaudi/github-actions/.github/workflows/component-semantic-release.yml explicitly requires .releaserc.json in the repo root; without it, semantic-release falls back to defaults that include @semantic-release/npm, whose verifyConditions step aborts on the missing package.json (this is a Go project, no npm). That's why the post-merge release on main failed. Restores the file verbatim from 372dcf3 (the pre-refactor main tip): explicit plugin list (no npm), breaking->minor / refactor->patch / chore->false release rules, chart Chart.yaml version+appVersion bump via @semantic-release/exec, CHANGELOG.md + chart/Chart.yaml committed back via @semantic-release/git. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Contributor
|
🎉 This PR is included in version 0.19.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
.releaserc.jsonto its pre-refactor content. The refactor's clean-slate sweep (bf522b4) deleted it; without it, semantic-release defaults to a plugin set that includes@semantic-release/npm, which aborts on the missingpackage.json. The reusable release workflow's own docstring requires this config.372dcf3:.releaserc.json(the last working main tip). Plugin list explicitly excludes npm; preserves the project's release-rule policy (breaking→minor, refactor→patch, chore→false) and the chart-version bump via@semantic-release/exec.Why the release failed on main
The post-
9c705deCI/CDrun (26269647417) showed:All other jobs (test, envtest, lint, build metadata) were green;
containerandhelmwere skipped because theyneeds: [release]. Once this file is restored, the next push tomain(the merge of this PR itself) re-runs the release pipeline, which should publish v0.19.0 (driven by the refactor'sfeat!:/refactor:commits sincev0.18.3).Heads-up — separate decision
The restored
breaking → minorrule is unusual; the standard convention isbreaking → major. Given v2alpha1 is a full API break, v1.0.0 would be the more honest version. If you want that instead of v0.19.0, this PR also needsbreaking: true→"major"AND the9c705demerge commit body would need aBREAKING CHANGE:footer (or a follow-up commit with one) so semantic-release picks it up. Not changed here — flagging only.Test plan
main—release / Semantic Releaseshould now succeedcontainer+helmjobs run and publish to GHCR🤖 Generated with Claude Code