fix(release): expose Telegram launcher failures safely#104099
Merged
Conversation
openclaw-barnacle
Bot
added
channel: telegram
…undary-diagnostics
openclaw-barnacle
Bot
removed
the
channel: telegram
Contributor
Author
|
Merged via squash.
|
github-actions Bot
pushed a commit
to Desicool/openclaw
that referenced
this pull request
Jul 11, 2026
* fix(release): expose Telegram launcher failures safely * test(release): prove namespace launcher diagnostics
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.
What Problem This Solves
The trusted Telegram release lane can fail before the isolated SUT writes its verified process identity, but the QA harness currently discards launcher stderr. The resulting generic error does not identify which isolation stage failed.
Why This Change Was Made
User Impact
No product behavior changes. Release maintainers get actionable, secret-safe Telegram SUT startup failures.
Evidence
actionlint .github/workflows/openclaw-release-telegram-qa.ymlgit diff --checktbx_01kx7gqns2kj85xqkr4wbgmhds: 88 focused tests passed across the QA extension and workflow contractpnpm check:changedpassed extension typechecks, extension/tooling lint, guards, and import-cycle checksNo agent transcript attached.