Document why channelEnvVars is retained despite the deprecation warning - #5
Merged
Conversation
The Plugin Inspector's channel-env-vars finding fires unconditionally on the presence of this field. On our supported OpenClaw range it is still the only source for env-driven channel-configured detection, so removing it would regress setup with no upside. Comment records why it stays and the exact condition under which it can be removed. No change to the generated manifest. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
Adds a comment (no functional change) in
scripts/build-manifest.mjsexplaining why the generated manifest keepschannelEnvVars, even though ClawHub's Plugin Inspector flags it with achannel-env-varsdeprecation warning at publish time.Why
Investigated the actual inspector (
@openclaw/plugin-inspector@0.3.18) and host (openclaw@2026.7.2-beta.3):channel-env-varsfinding fires unconditionally wheneverchannelEnvVarsis non-empty — there is no "covered by setup metadata" check, and anopenclaw.setupEntrydoes not suppress it. The only way to clear it is to remove the field.>=2026.7.2-beta.3, which is currently the newest published OpenClaw),channelEnvVarsis the only sourceresolveChannelEnvVarsreads. It powersisStaticallyChannelConfigured(detecting the channel as configured fromAGENTMAIL_API_KEYin the env) and the env-shell expected-keys surface.The warning is therefore an expected, forward-looking deprecation notice — not a defect. The comment records this and the exact condition under which the field can be removed (once the minimum supported OpenClaw reads channel env names from the newer setup model, at which point the floor is raised to match).
Verification
node scripts/build-manifest.mjs --check→openclaw.plugin.json is up to date(comment does not change generated output).🤖 Generated with Claude Code