Skip to content

fix(release): point configSchema back to config.d.ts - #74

Merged
tembleking merged 1 commit into
mainfrom
fix/config-schema
Sep 28, 2026
Merged

tembleking merged 1 commit into
mainfrom
fix/config-schema

Conversation

@tembleking

Copy link
Copy Markdown
Member

1.5.3 shipped without any config schema file, breaking the app build for consumers (missing config.schema.json).

Root cause: ff5cb35 committed the package.json as rewritten by backstage-cli package prepack (configSchema: config.schema.json). With the source already pointing at the JSON, prepack had nothing to generate, so the tarball referenced a file that didn't exist.

Pointing back to config.d.ts lets prepack generate config.schema.json at publish time again (verified with npm pack). Bumps to 1.5.4 to trigger the release.

1.5.3 shipped without any config schema file because ff5cb35 committed the package.json as rewritten by backstage-cli prepack (configSchema: config.schema.json). With the source already pointing at the JSON file, prepack had nothing to generate, so the tarball referenced a missing file and broke consumers' app builds.

Pointing back to config.d.ts lets prepack generate config.schema.json at publish time again. Bumps to 1.5.4 to trigger the release.
@tembleking
tembleking enabled auto-merge (squash) September 28, 2026 14:28
@tembleking
tembleking merged commit c951156 into main Sep 28, 2026
2 checks passed
@tembleking
tembleking deleted the fix/config-schema branch September 28, 2026 14:57
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