fix(release): point configSchema back to config.d.ts - #74
Merged
Merged
Conversation
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
enabled auto-merge (squash)
September 28, 2026 14:28
airadier
approved these changes
Sep 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.jsonas rewritten bybackstage-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.tslets prepack generateconfig.schema.jsonat publish time again (verified withnpm pack). Bumps to 1.5.4 to trigger the release.