chore(release): @webjsdev/cli 0.9.0 + @webjsdev/server 0.7.3

changelog/cli/0.9.0.md

@@ -0,0 +1,29 @@
+---
+package: "@webjsdev/cli"
+version: 0.9.0
+date: 2026-05-25T08:47:54.016Z
+commit_count: 2
+---
+## Breaking
+
+- **Default `webjs dev` / `webjs start` port is now 8080 (was 3000)** ([#97](https://github.com/webjsdev/webjs/pull/97)) [`7c44e6e`](https://github.com/webjsdev/webjs/commit/7c44e6e)
+
+  3000 is heavily contested locally (Next.js, CRA, Express, Flask all
+  default there), so newly scaffolded apps now serve on 8080.
+  `process.env.PORT` still wins, so deploys that inject `PORT` (Railway,
+  Fly, Heroku, etc.) are unaffected.
+
+  **Migration:** to keep the old port, set `PORT=3000` (or pass
+  `--port 3000`) when running `webjs dev` / `webjs start`. Scaffolded
+  apps need no change.
+
+## Fixes
+
+- **Resolve the @webjsdev/ui registry via the module resolver, not path math** ([#95](https://github.com/webjsdev/webjs/pull/95)) [`f01059b`](https://github.com/webjsdev/webjs/commit/f01059b)
+
+  `webjs create` located the UI registry with `__dirname/../../ui/packages/registry`,
+  which assumed @webjsdev/ui was hoisted as a sibling of @webjsdev/cli. That
+  broke on non-hoisted layouts (pnpm's isolated linker, `npm install
+  --install-strategy=nested`, some CI setups), failing the scaffold. It now
+  resolves the registry through `require.resolve`, so `webjs create` works
+  regardless of install layout.

changelog/server/0.7.3.md

@@ -0,0 +1,16 @@
+---
+package: "@webjsdev/server"
+version: 0.7.3
+date: 2026-05-25T08:47:53.970Z
+commit_count: 1
+---
+## Changes
+
+- **`startServer` default port and OAuth fallback origin moved to 8080** ([#97](https://github.com/webjsdev/webjs/pull/97)) [`7c44e6e`](https://github.com/webjsdev/webjs/commit/7c44e6e)
+
+  `startServer({ appDir })` without an explicit `port` now defaults to 8080
+  (was 3000), matching the new `@webjsdev/cli` default, and the OAuth
+  no-request fallback origin moved from `localhost:3000` to `localhost:8080`.
+  `process.env.PORT` and an explicit `port` option still win. The recommended
+  `createRequestHandler` embedding path is unaffected (the host server owns
+  the port there).

packages/cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@webjsdev/cli",
-  "version": "0.8.6",
+  "version": "0.9.0",
   "type": "module",
   "description": "webjs CLI - dev, start, create, db",
   "bin": {

packages/server/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@webjsdev/server",
-  "version": "0.7.2",
+  "version": "0.7.3",
   "type": "module",
   "description": "webjs dev/prod server: SSR, router, API, server actions, live reload",
   "main": "index.js",