Skip to content

fix(relay): document why command output is no longer relayed - #61

Merged
zznathans merged 1 commit into
mainfrom
fix/trigger-release-for-relay-revert
Aug 4, 2026
Merged

fix(relay): document why command output is no longer relayed#61
zznathans merged 1 commit into
mainfrom
fix/trigger-release-for-relay-revert

Conversation

@zznathans

Copy link
Copy Markdown
Owner

Summary

Test plan

  • CI - pending on this PR.
  • Confirm a new BeBot version is cut and released after merge.
    Co-Authored-By: Claude Sonnet 5 noreply@anthropic.com

The previous commit reverting the relay hook (#60) used a "revert:" commit
type, which semantic-release's default Angular rules don't treat as
release-triggering - no new version/image was cut, so the revert never
actually reached production. This fix-typed commit (documenting the
reverted behavior in a comment, for anyone wondering why the hook isn't
there) triggers the release that carries the actual revert out to a
deployable image.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@github-actions github-actions Bot added core Core bot framework (Main/**) commodity-base-passive-module labels Aug 4, 2026
@zznathans
zznathans merged commit dfc03d4 into main Aug 4, 2026
15 checks passed
@zznathans
zznathans deleted the fix/trigger-release-for-relay-revert branch August 4, 2026 21:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

commodity-base-passive-module core Core bot framework (Main/**)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant