Release v1.7.0: rescue the orphaned v1.6.0, bundled types, changelog - #6
Merged
Conversation
…actions slot, Card sm size Additive package changes for the app-wide frontend consistency refactor: - Promote CodeEditor (replacing the app's JsonEditor/MarkdownEditor) and FullscreenPanel into the kit, both lazy-loading CodeMirror consistently with CodePreview's existing convention. - Add an optional #actions slot to PageHeading and a purple legacy tone alias to StatusBadge, closing gaps the app was working around locally. - Add a Card size="sm" variant for nested/compact container use. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
v1.6.0 was tagged and published from 3472cdf but never merged, so main lost CodeEditor, FullscreenPanel, Card's sm size, the PageHeading actions slot and the CodePreview changes — 407 lines that consumers on ^1.6.0 already depend on. Releasing anything from main without this would silently regress them.
Version 1.7.0 rather than 1.6.0: that version is already tagged and published, so it cannot be republished. 1.7.0 is the first release whose `main` actually contains the v1.6.0 work, which until the preceding merge existed only on an orphaned tag. Adds CHANGELOG.md and moves the release notes out of the README, which had accumulated three "What's new in …" sections and the v1.3.0 migration notes. Versions between those and now had no notes at all; the gaps are filled from each release commit rather than invented, and v1.4.0 is marked superseded since v1.4.1 exists only to revert it. Documents the tokenless git-dependency install in the README, and corrects the claim there that a token is needed because the package is private — it is needed because GitHub's npm registry authenticates every read, public or not. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
vite-plugin-dts 5 renamed the option and accepts-and-ignores the old name rather than rejecting it, so `rollupTypes: true` had silently stopped doing anything after the dependency bump. The build was emitting split per-component declarations: dist/index.d.ts fell from ~84 KB to 9 KB, with the real types moved into a dist/components tree. Importing from the package still resolved, which is why nothing failed — but a consumer that reads the declaration file to check its own usage against the public API got a valid-looking file describing almost nothing. Found exactly that way: llm-gateway's design-system prop checker silently matched zero components and passed every file. Adds @microsoft/api-extractor, which bundleTypes requires and which was previously only present transitively. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Storybook inherits vite.config.ts, so enabling `bundleTypes` also pointed API Extractor at the docs build, where it walks the stories and dies on Vue's internal template symbols: "Symbol not found for identifier: __VLS_1". The library build was fine; `build-storybook` was not, which broke CI. This build has no declarations to emit, so the plugin is filtered out in viteFinal rather than made conditional in vite.config.ts — that keeps the library build's own config honest instead of teaching it about Storybook. Missed locally because build-storybook had been run before `bundleTypes` was enabled and the Playwright suite then served that already-built storybook-static, so both looked green against a stale artefact. Re-verified by running the CI steps in order from a clean npm ci: typecheck, lint, build (index.d.ts 84 KB bundled), build-storybook, 192 Playwright tests. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Follow-up to #5, which was merged while three further commits were still in flight.
maincurrently has only the first of them, so it is still on1.5.0and still missing the work below.mainhad lost the published v1.6.0 — the important onev1.6.0was tagged and published from a commit that was never merged.mainwas therefore missing 437 lines that consumers on^1.6.0already depend on:CodeEditor,FullscreenPanelCard'ssmsizePageHeadingactions slotCodePreviewrefinements,useEscapeKey,codeMirrorThemeAnything released from
mainbefore this merge would have silently regressed them —llm-gatewayuses<Card size="sm">, which does not exist onmain.Version 1.7.0, not 1.6.0
1.6.0 is already tagged and published, so it cannot be republished. 1.7.0 is the first release whose
mainactually contains that work.Types are a single bundled
index.d.tsagainvite-plugin-dts5 renamedrollupTypes→bundleTypesand ignores the old name rather than rejecting it, so the build had quietly started emitting split per-component declarations:dist/index.d.tsfell from ~84 KB to 9 KB with the real types moved into adist/components/tree.Importing from the package still resolved, which is why nothing failed. But a consumer that reads the declaration file to check its own usage got a valid-looking file describing almost nothing — found exactly that way, when llm-gateway's prop checker reported "clean against 0 components". Adds
@microsoft/api-extractor, whichbundleTypesrequires.CHANGELOG.mdRelease notes move out of the README. Gaps between v1.3.0 and now are filled from each release commit rather than invented, and v1.4.0 is marked superseded since v1.4.1 exists only to revert it.
Verified
npm cisucceeds ·npm audit0 vulnerabilitiesbuild,lint,typecheckclean ·index.d.tsback to 84 KB bundledbuild-storybooksucceeds · 192 Playwright tests passGITHUB_TOKENand no.npmrcAfter merging
Tag and release
v1.7.0so the registry and the git-dependency route both have it:git tag v1.7.0 && git push --tags🤖 Generated with Claude Code