Skip to content

fix(scripts): drop the oxfmt pass on gitignored schema files - #2630

Merged
dyoshikawa merged 1 commit into
mainfrom
fix/generate-schema-oxfmt-gitignore
Aug 8, 2026
Merged

fix(scripts): drop the oxfmt pass on gitignored schema files#2630
dyoshikawa merged 1 commit into
mainfrom
fix/generate-schema-oxfmt-gitignore

Conversation

@dyoshikawa

Copy link
Copy Markdown
Owner

Problem

The Publish Assets workflow for the v16.9.0 release failed at the pnpm generate:schema step:

Expected at least one target file. All matched files may have been excluded by ignore rules.
Error: Command failed: npx --no-install oxfmt config-schema.json mcp-schema.json permissions-schema.json

Since oxfmt 0.62.0 (bumped in #2606), gitignored paths are skipped even when passed explicitly, and --ignore-path does not override this. The three generated schema files are gitignored, so the formatter pass now fails.

Solution

Drop the runOxfmt call from generate-json-schema.ts. The schema files are already written with deterministic JSON.stringify(..., null, 2) output and have no drift check (they are gitignored release assets), so the formatter pass was cosmetic only. Also document the tracked-files-only constraint in run-oxfmt.ts, whose remaining callers (docs content, supported-tools tables) all format tracked files.

Unblocks the v16.9.1 release (v16.9.0 assets were never built; npm still has 16.8.0).

🤖 Generated with Claude Code

Since oxfmt 0.62.0, gitignored paths are skipped even when passed
explicitly, so the formatter pass in generate-json-schema.ts failed with
"Expected at least one target file" and broke the Publish Assets
workflow. The schema files are already written with deterministic
JSON.stringify output and have no drift check, so the pass is dropped.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@dyoshikawa
dyoshikawa merged commit 065b883 into main Aug 8, 2026
10 checks passed
@dyoshikawa
dyoshikawa deleted the fix/generate-schema-oxfmt-gitignore branch August 8, 2026 07:36
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.

2 participants