Skip to content

release: prepare 0.3.0 breaking release - #43

Merged
smiggleworth merged 5 commits into
mainfrom
refacto/0.3.0-breaking
Sep 11, 2026
Merged

smiggleworth merged 5 commits into
mainfrom
refacto/0.3.0-breaking

Conversation

@smiggleworth

@smiggleworth smiggleworth commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Move @askrjs/node, @askrjs/server, and the @askrjs/askr peer to >=0.3.0 <0.4.0.
  • Narrow vite-plus from ^0.2.8 || ^0.3.0 to ^0.3.1.
  • Delete tests/smoke.test.js; update tests/architecture.test.js.

Package version: 0.2.2 → 0.3.0.

Breaking changes

  • vite-plus 0.2.x is no longer supported.

Release coordination

Part of the coordinated 0.3.0 breaking release across the Askr package set.

  • Publish wave 5 of 5.
  • Cannot be published until wave 4 is on npm.

Review fixes

  • tests/architecture.test.js asserted a vite-plus peer range of ^0.3.0 while package.json declares ^0.3.1; the assertion now matches the manifest. It would have failed as soon as CI could install.
  • Restored tests/smoke.test.js, which covers the SPA plugin export shape.

Local: 67/67 tests pass.

Validation

  • CI is red at the npm ci / vp install step with ETARGET … 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.json still resolves @askrjs/* at 0.2.x. The lockfile needs regenerating once the upstream packages are on npm — publishing alone will not turn this check green.

The architecture test asserted a vite-plus peer range of ^0.3.0 while
package.json declares ^0.3.1 in all three places it appears, so the test would
have failed as soon as CI could install. Assert the range that is actually
declared.

Also restore tests/smoke.test.js, which covers the SPA plugin export shape and
was deleted without replacement.
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.
@smiggleworth
smiggleworth merged commit dcea339 into main Sep 11, 2026
3 checks passed
@smiggleworth
smiggleworth deleted the refacto/0.3.0-breaking branch September 11, 2026 22:53
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.

1 participant