Repository navigation
release: prepare 0.3.0 breaking release - #61
Merged
Merged
Conversation
Every other repo in the 0.3.0 release declares its siblings as >=0.3.0 <0.4.0; the website pinned all 17 to an exact 0.3.0. Exact pins mean every patch release across the package set needs a website commit to pick up. Match the convention used everywhere else.
smiggleworth
force-pushed
the
refacto/0.3.0-breaking
branch
from
September 11, 2026 20:58
99e3c96 to
93526f1
Compare
The 0.3.0 prep bumped the declared ranges but left the resolved tree pinned at 0.2.x, so npm ci could not satisfy package.json. Re-resolve now that the upstream packages are on npm.
Regenerate the package snapshot against the published 0.3.0 set. It drops the removed themes layout aliases (Box, Inline, Shell, ShellNav, ShellMain) and moves every recorded version to 0.3.0. Two follow-ons that surfaced with it: - askr 0.3.0 adds hasState and state to RouteSnapshot, so the route-analytics fixture no longer satisfied the type. - The refreshed manifest exposes @askrjs/ui/overlay-host, which the previous snapshot predated. Map it to the existing portals-and-layers guide so every published entrypoint still resolves to authored docs.
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.
Summary
@askrjs/*dependencies to an exact0.3.0.Release coordination
Part of the coordinated
0.3.0breaking release across the Askr package set.Review fixes
0.3.0pins to>=0.3.0 <0.4.0, matching the convention every other repo in this release uses.Validation
npm ci/vp installstep withETARGET … no matching version found for @askrjs/…@>=0.3.0 <0.4.0. This is expected until the upstream wave publishes; it is not a code failure.package-lock.jsonstill resolves@askrjs/*at0.2.x. The lockfile needs regenerating once the upstream packages are on npm — publishing alone will not turn this check green.