Skip to content

fix(ci): reusable validate secret must be schema_token (not schema-token) - #279

Merged
ChrisonSimtian merged 1 commit into
mainfrom
fix/validate-secret-name
Jul 20, 2026
Merged

fix(ci): reusable validate secret must be schema_token (not schema-token)#279
ChrisonSimtian merged 1 commit into
mainfrom
fix/validate-secret-name

Conversation

@ChrisonSimtian

Copy link
Copy Markdown
Collaborator

Follow-up fix to D2 (#276). GitHub secret identifiers allow only alphanumerics + underscore — a hyphen in a workflow_call secrets: key is invalid, so schema-token would reject the reusable-workflow call.

  • _validate-shapes.yml: schema-tokenschema_token (secret declaration + GH_TOKEN env ref + caller example comment).
  • Inputs (schema-ref, shapes-path) keep hyphens — allowed for inputs, only secrets are restricted.

The SmartHome caller (#278) already uses schema_token, so once this + SCHEMA_RO_PAT land, the opt-in validation goes green.

Refs #272.

🤖 Generated with Claude Code

GitHub secret identifiers allow only alphanumerics + underscore — a hyphen in a
workflow_call `secrets:` key is invalid, so `schema-token` would reject the
call. Rename to schema_token (declaration + env ref + caller example). Inputs
(schema-ref/shapes-path) keep hyphens — those are allowed for inputs.

The Homelab.Stacks.SmartHome caller (#278) already uses schema_token.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@ChrisonSimtian
ChrisonSimtian merged commit 0cbaee1 into main Jul 20, 2026
@ChrisonSimtian
ChrisonSimtian deleted the fix/validate-secret-name branch July 20, 2026 08:34
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