Skip to content

chore(ci): fix spec-check download step (gh api has no -o flag)#13

Merged
caballeto merged 1 commit into
mainfrom
chore/fix-spec-check-output-flag
May 1, 2026
Merged

chore(ci): fix spec-check download step (gh api has no -o flag)#13
caballeto merged 1 commit into
mainfrom
chore/fix-spec-check-output-flag

Conversation

@caballeto
Copy link
Copy Markdown
Contributor

Summary

  • gh api ... -o <file> has never worked — gh api has no -o flag (it's gh release download that does). Every spec_updated auto-dispatch from mono would have bailed with unknown shorthand flag: 'o' before running codegen, which explains why no auto-regen PR has ever landed on this repo after a mono spec change.
  • Swapped to a > <file> redirect. Verified the spec still streams as raw JSON via the Accept: application/vnd.github.raw+json header that was already set.

Caught while debugging why the recent forensic spec change on mono didn't produce an auto-regen PR here.

Test plan

  • Merge and let the next mono spec dispatch exercise the workflow (or manually trigger via gh api repos/devhelmhq/<this>/dispatches -f event_type=spec_updated with a PAT that has workflow scope).

Made with Cursor

`gh api ... -o <file>` silently errored ("unknown shorthand flag: 'o'")
on every invocation, so every mono-dispatched spec_updated event that
reached this repo would have bailed on the download step before
regenerating types. Switched to a `> <file>` redirect.

Discovered while debugging why the forensic spec change on mono didn't
produce auto-regen PRs here.

Made-with: Cursor
@caballeto caballeto merged commit 6e9a4aa into main May 1, 2026
4 checks passed
@caballeto caballeto deleted the chore/fix-spec-check-output-flag branch May 1, 2026 13:14
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