chore: release server 0.8.46, cli 0.10.36#880
Conversation
vivek7405
left a comment
There was a problem hiding this comment.
Release checks out. Both bumps are patch and stay inside the ^0.8.0 / ^0.10.0 dependent ranges, the changelogs match the real changes and their hashes resolve, and the not-bumped packages (core/mcp/intellisense only cosmetic casing + docs, ui only the nested website) genuinely carry nothing releasable. One thing I confirmed and noted in the body: the lockfile resync also corrects a stale core entry (0.7.30 to 0.7.32) to match core's already-current package.json, so core is not re-released, only server and cli publish. Clean.
vivek7405
left a comment
There was a problem hiding this comment.
Confirmed the publish path: release.yml keys on added changelog/**.md files (--diff-filter=A), and the diff adds exactly two (server 0.8.46, cli 0.10.36), so only those publish. Frontmatter versions and counts match the bumped package.json files. Ready to merge.
Release the accumulated unreleased work on
@webjsdev/serverand@webjsdev/cli. Merging this adds thechangelog/**.mdfiles tomain, which triggersrelease.ymltonpm publishboth packages and cut GitHub Releases.@webjsdev/server 0.8.45 -> 0.8.46 (patch)
route()now accepts the action's module namespace and auto-applies its declaredmiddleware+validate, so a guard declared once protects the RPC and REST boundaries alike (from fix: dogfood triage (route() middleware, scaffold typecheck, scaffold a11y) #879).@webjsdev/cli 0.10.35 -> 0.10.36 (patch)
webjs typecheckand returns zero axe violations out of the box (from fix: dogfood triage (route() middleware, scaffold typecheck, scaffold a11y) #879).Not bumped (checked all published packages)
packages/ui/packages/website(the nested website), not the published@webjsdev/uisurface.Notes
^0.8.0/^0.10.0dependent caret ranges, so no dependent range edits.package-lock.jsonresynced (it was stale on main). The diff is three workspace version lines: server -> 0.8.46 and cli -> 0.10.36 (the bumps), plus core 0.7.30 -> 0.7.32 correcting the lockfile to core's already-current package.json (core itself is NOT re-released; only the server and cli changelog files trigger a publish).release.ymlowns them.Changelogs:
changelog/server/0.8.46.md,changelog/cli/0.10.36.md.