Skip to content

πŸ› fix(ci): escape ${{ in composite action description#119

Merged
ZaxShen merged 1 commit into
devfrom
fix/116-composite-action-description-escape
Apr 26, 2026
Merged

πŸ› fix(ci): escape ${{ in composite action description#119
ZaxShen merged 1 commit into
devfrom
fix/116-composite-action-description-escape

Conversation

@ZaxShen
Copy link
Copy Markdown
Contributor

@ZaxShen ZaxShen commented Apr 26, 2026

Hotfix for #118.

Bug

PR #118's composite action loaded with:
```
##[error]/home/runner/work/plugin/plugin/./.github/actions/verify-cc-auth/action.yml (Line: 2, Col: 14): Unrecognized named-value: 'secrets'.
```

The `description:` field literally contained `token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}` as a usage example. GitHub Actions evaluates expressions even inside the description field β€” and composite actions don't have access to the `secrets` context (only `inputs`), so the action loader exploded.

Fix

Strip the `${{ secrets... }}` example out of the description field. Keep description as plain prose.

(Could also have escaped via `$${{...}}` but removing the example is cleaner β€” anyone reading the action source sees the inputs schema directly.)

Verify

After merge, re-trigger `gh workflow run l6-dogfood.yml --ref dev`. The composite should load and run the auth check.

πŸ€– Generated with Claude Code

@ZaxShen ZaxShen merged commit 7be0f53 into dev Apr 26, 2026
2 checks passed
@ZaxShen ZaxShen deleted the fix/116-composite-action-description-escape branch April 26, 2026 19:15
ZaxShen added a commit that referenced this pull request May 20, 2026
…#118 + #119)

Two tightly-coupled fixes from 2026-04-29 L0-L5 verification:
- #118: scripts/hooks/write-active-workspace-sentinel.sh was committed
  at mode 100644 (sibling hooks are 100755). Production regression
  from #113. Chmod fix.
- #119: L0 install-smoke executable-check used (echo FAIL && exit 1)
  in a subshell, so build kept going past the FAIL. Replace with
  set -e + brace-group { ...; exit 1; } so exit propagates.

Without #119, #118 would have shipped silently (the build didn't fail
when the bug existed). Pairing them keeps the verification chain
honest going forward.
ZaxShen added a commit that referenced this pull request May 20, 2026
πŸ› fix(install-smoke): chmod +x sentinel hook + propagate L0 assertion (#118 + #119)

See merge request trustmybot/plugin!39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant