Docs(osa) slash compat and release recovery note#10
Merged
Conversation
Update docs and agent hints that slash commands don't work with all channels, such as Slack
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (2 files)
Reviewed by gpt-5.4-2026-03-05 · 611,304 tokens |
…unner-sha> && git push origin vX.Y.Z. That doesn't work because: - The commit was built inside the runner by publish.yml:185 (git commit -m "release: $TAG") - When the push was rejected, that commit object lives only in the (now-destroyed) runner; the operator's local clone has no way to fetch it - git tag <sha> fails with "unknown revision" on any SHA git doesn't know Corrected: when the tag is missing, point readers at Scenario 4 (which already documents the correct reconstruct-and-tag flow — bump package.json locally to the published version, commit, tag, push). Also noted that the workflow's Print recovery instructions on partial failure step prints this same sequence inline in the failed run's logs.
jeanduplessis
approved these changes
Apr 20, 2026
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
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
Docs-only PR covering three related areas the last two releases exposed as gaps:
Slash-command channel compatibility. Documents that
/security-checkupworks in the OpenClaw native control UI chat and Telegram, but not in Kilo Chat or Slack (those channels don't route OpenClaw slash commands). Kilo Chat / Slack users should invoke the plugin via natural language so the agent calls thekilocode_security_advisortool directly. The tool description now tells the agent not to suggest/security-checkupin those channels.Path-agnostic update reminder. Security checkup reports now occasionally append a "stay current" footer with
npm view @kilocode/openclaw-security-advisor versionand the upgrade commands. The footer is applied indoCheckupat the markdown layer, so it surfaces on both the LLM-drivenkilocode_security_advisortool path and the LLM-bypassing/security-checkupslash command path — fixing an earlier approach that lived only in the tool description and would never have reached slash-command users. Cadence is roughly 1-in-5 successful reports. README has a newStaying up to datesection documenting the commands.Release recovery banner. Documents the current partial-publish failure mode (
github-actions[bot]not on themainruleset's bypass list → every stable publish fails at the post-publish push step withGH013). Gives a clean 3-step recovery:gh release create --verify-tagcommand.--verify-tagis critical — without it,gh release createsilently mints a missing tag at currentmainHEAD, pointing the release at code that was never published to npm.RELEASING.md'sBranch protectionsection now also lists the two durable fixes (add the bot to the bypass list, or refactor stable publishes to never touchmain).Test plan
bun run typecheck— passesbun run format:check— passesbun test— 44 pass / 0 fail🤖 Generated with Claude Code