release: prepare 0.3.0 breaking release - #41
Merged
Merged
Conversation
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.
@askrjs/server 0.3.0 drops the routes option in favour of router.routes, so these fixtures no longer compile (askr-node) or resolve their route at all (askr-testing, which returned a problem document instead of the handler body). Build the routes through createRouter, which is the form the rest of these suites already use.
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/auth,@askrjs/server, and@askrjs/schemato>=0.3.0 <0.4.0. No source changes.Package version:
0.2.1 → 0.3.0.Release coordination
Part of the coordinated
0.3.0breaking release across the Askr package set.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.