ci: stop unconfigured-publisher noise (remove Telegram + fail-safe npm/ClawHub)#7
Merged
Conversation
added 2 commits
May 28, 2026 16:15
The Telegram notifier isn't configured (no bot token/chat) and fails on every tag push — including prerelease/RC pushes — producing useless red alerts. Remove it. (The product-level Telegram backup feature, smem_telegram_backup, is unaffected — this only deletes the CI notification workflow.)
The release publishes only to PyPI + GitHub today; npm (plugin + SDK), ClawHub, and VS Code were never configured (no/invalid tokens, npm package names don't exist) and were failing — ClawHub even reddened the whole release because its `clawdhub login` wasn't guarded. Guard every optional publisher so a missing secret is a clean skip (notice), and a failed publish is a warning, never a red build: - release.yml: ClawHub (skip if no CLAWHUB_TOKEN + guard login), npm + SDK (skip if no NPM_TOKEN, tolerant publish). - publish-npm.yml / publish-sdk.yml (rolling RC): skip if no NPM_TOKEN so they stop failing on every push to main. PyPI + GitHub Release are unaffected and remain the live channels (where 2.0.0 and 2.1.0 actually shipped).
acidkill
changed the title
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
Stop CI going red on publish channels that were never configured. Today only PyPI + GitHub Release are live (where 2.0.0 and 2.1.0 actually shipped); npm (plugin + SDK), ClawHub and VS Code have no working tokens / the npm package names don't even exist yet.
.github/workflows/notify-telegram.yml— not configured, fails on every tag/RC push.::notice), a failed publish is a::warning, never a red build:release.yml: ClawHub (skip if noCLAWHUB_TOKEN; its unguardedclawdhub loginwas what reddened thev2.1.0release), npm + SDK (skip if noNPM_TOKEN, tolerant publish).publish-npm.yml/publish-sdk.yml(rolling RC): skip if noNPM_TOKENso they stop failing on every push tomain.PyPI + GitHub Release are untouched.
Context (diagnosed)
surreal-memoryon PyPI:2.0.0and2.1.0— release works.surrealmemory,@acidkill/surreal-memory-client,@surrealmemory/openclaw-plugin→ all 404 (don't exist); npm was never actually published for any version.CLAWHUB_TOKENempty → "Token required".Test plan
telegramreferences left under.github/