Repository navigation
chore: release main - #43
github-actions[bot] wants to merge 1 commit into
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
… every change (#47) The 0.6.0 release PR (#43) failed "kube adapter (go)": gateway/kube/go.mod requires gateway v0.6.0, whose tag does not exist until the PR merges, and workspace mode still reads the required version's go.mod ("unknown revision gateway/v0.6.0"). main never requires an untagged version, so nothing caught it. - go.work replaces the core at exactly the version the adapter requires (Go refuses an unversioned replace of a workspace module). The line carries x-release-please-version, and Release Please updates /go.work with gateway/kube/go.mod. - .github/scripts/release-rehearsal.mjs applies Release Please's own version regex to every marked line with a version that is never tagged (0.999.0), vets and builds the adapter, and restores the files. It fails if go.work and the adapter's requirement disagree. It runs in CI's kube job and in task verify. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
|
Closing so release-please regenerates the 0.6.0 release PR. It reported "PR #43 remained the same" after #47: it only refreshes an open release PR when its release notes change, and #47 was a |
🤖 I have created a release beep boop
@configbutler/krm-stream: 0.6.0
0.6.0 (2026-10-02)
Features
gateway: 0.6.0
0.6.0 (2026-10-02)
Features
gateway/kube: 0.6.0
0.6.0 (2026-10-02)
Features
This PR was generated with Release Please. See documentation.