chore: release core 0.7.48, server 0.8.60, cli 0.10.52 and mcp 0.1.12 - #1318
Merged
Conversation
Clears the four packages carrying unreleased work since 0.7.47. The other tracked packages (ui, intellisense, and the two editor packages) picked up nothing user-facing in the range: ui's only change was a corrected doc block and its test, so bumping it would ship an empty changelog. Three features and two fixes ride along. The bound-form submitter now carries its own submission (#1317): a `formaction=${action}` button gains its own `formmethod` and enctype rather than relying on the enclosing form's start tag, so it works in a bound form, an unbound form, a `method="get"` form, or no form at all. That deletes the silent-GET failure the previous release could only report, and reverses the part of #1207 that refused a plain button's own `formmethod`. The client router also sends the enctype the author declared, which a plain `<form method="post">` never got: it sent urlencoded with JS off and multipart with JS on. The elision verdict becomes inspectable (#1312): `webjs elision` prints the per-module verdict with the evidence behind every ship, `--json` emits it, `--verify` diffs masked SSR bytes with `WEBJS_ELIDE` flipped across the app's own route corpus, and the same report reaches `webjs doctor` and the MCP `list_elision` tool. SSR action seeding becomes observable in dev (#1311) through `X-Webjs-Seed`, the access log, and a browser warning that names only causes it can prove. Raises packages/server's declared `@webjsdev/core` range from ^0.7.47 to ^0.7.48. No new core export is imported statically, so this is not the load-time skew the rule was written for, but both features span the two packages over a shared wire contract (the seed header and marker that core's client reads, the submitter attributes SSR emits and core's renderer commits), and the release PR is the only place that bump is legal. The generated notes were curated before committing: each entry is rewritten to the package's own slice rather than the shared commit subject, the seeding feature's fourteen follow-up fixes are folded into the feature they hardened, and the cli entry is narrowed to what actually changed in the scaffold.
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
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.
Clears the four packages carrying unreleased work since the 0.7.47 batch.
@webjsdev/core@webjsdev/server@webjsdev/cli@webjsdev/mcpNot bumped, deliberately.
@webjsdev/ui,@webjsdev/intellisenseand thetwo editor packages picked up nothing user-facing in the range. The only ui
change was a corrected doc block in
src/registry/fetcher.jsplus its test,landed under a
chore:subject, so a bump would ship an empty changelog andthe backfill would refuse to write one.
What ships
A bound submitter carries its own submission (#1317). A
formaction=${action}button gains its ownformmethod="post"plusformenctyperather than relying on the enclosing form's start tag, so itworks inside a bound form, an unbound form, a
method="get"form, or no format all. That deletes the silent-GET failure the previous release could only
report, and it reverses the part of #1207 that refused a plain button's own
formmethod, since the client router already honoured it with nativeprecedence. The client router also sends the enctype the author declared: a
plain
<form method="post">used to send urlencoded with JS off and multipartwith JS on, one template making two different requests.
The elision verdict is inspectable per app (#1312).
webjs elisionprintsthe per-module verdict with the evidence behind every ship,
--jsonemits itfor a tool, and
--verifyboots two handlers withWEBJS_ELIDEflipped anddiffs the masked SSR bytes across the app's own static route corpus, exiting
non-zero on a divergence and on a corpus where nothing was compared. The same
report reaches
webjs doctoras a component check and MCP aslist_elision.The orphan scan's false positives are fixed in both packages.
SSR action seeding is observable in dev (#1311).
X-Webjs-Seedplus aseedfield in the access log, and a browser warning that names only causes itcan prove. Seed ingestion flips to last-write-wins, with the drain-and-evict
work that makes it safe across a soft navigation and a
<webjs-frame>swap.Fixes. Back-button restore survives late layout growth (#1313), and
removeBetweenno longer leaks one orphan comment node per teardown (#1292).Publish ordering
changelog/core/0.7.48.mdcarries the earliestdate:of the batch, so thepublish loop ships core first.
packages/server's declared@webjsdev/corerange goes from ^0.7.47 to^0.7.48. No new core export is imported statically, so this is not the
load-time skew the rule was written for. Both features span the two packages
over a shared wire contract though (the seed header and
data-webjs-devmarkercore's client reads, the submitter attributes SSR emits and core's renderer
commits), and the release PR is the only place that bump is legal.
Notes curation
The generated entries were rewritten before committing: each package's entry
describes its own slice rather than repeating the shared commit subject, the
seeding feature's fourteen follow-up fixes are folded into the feature they
hardened, and the cli entry is narrowed to what actually changed in the
scaffold (a guidance comment, not the action).