Skip to content

chore: release core 0.7.51, server 0.8.64 and ui 0.3.14 - #1415

Merged
vivek7405 merged 1 commit into
mainfrom
chore/release-2026-08-15
Aug 15, 2026
Merged

chore: release core 0.7.51, server 0.8.64 and ui 0.3.14#1415
vivek7405 merged 1 commit into
mainfrom
chore/release-2026-08-15

Conversation

@vivek7405

@vivek7405 vivek7405 commented Aug 15, 2026

Copy link
Copy Markdown
Collaborator

Clears every package carrying unreleased user-facing work since 0.7.50.

core adds refreshPage, which re-renders the current url on the server and
applies it in place with no reload, no history entry and no scroll, and
prefetches a link that drives a frame in that frame's own dimension so the
click costs no round trip. The fix records a same-document history entry
before the swap rather than after, which is what made an iOS swipe-back
preview the page the user was already on.

server stops a dev edit to a page or layout reloading the browser, so hydrated
state and scroll survive a save, and marks a sliced frame response so the
client can tell a real subtree from a whole document. The fixes render an
error boundary inside its own layout chain, coalesce a burst of dev reload
signals so rapid edits stop leaving the page unstyled, and root the vendor
specifier scan in the module graph.

ui takes the a11y fix alone.

Three packages are deliberately absent. cli, mcp and intellisense carry no
user-facing change in the range. cli's only such commit was #1414, which #1417
reverted in full, so what remains is the doctor barrel split, an internal move
with an unchanged export surface. mcp picked up three doc-string edits from
the same refactor, naming the new sibling-directory paths its source tool can
read, and the paths it already documents still resolve because they are
barrels. intellisense picked up nothing at all.

Raises packages/server's declared @webjsdev/core range from ^0.7.50 to
^0.7.51. The dev refresh reads refreshPage through a runtime feature check
rather than a static import, so nothing breaks without it, but the release PR
is the only place that bump is legal and core carries the earliest date in the
batch so it publishes first.

core and server carry the generated notes verbatim. ui is edited twice, both
because the generator reads conventional-commit prefixes and cannot see
anything else. It wrote #1414 into the entry for work #1417 has since reverted,
which is removed along with the Features section it emptied; and its excerpt is
the first lines of a squashed message, which for #1412 opened on the CDP
measurement instrument rather than on the fix, so the fix sub-commit takes its
place.

@vivek7405
vivek7405 force-pushed the chore/release-2026-08-15 branch from 8107391 to 8a2f251 Compare August 15, 2026 05:38
@vivek7405 vivek7405 changed the title chore: release core 0.7.51, server 0.8.64, cli 0.10.56 and ui 0.3.14 chore: release core 0.7.51, server 0.8.64 and ui 0.3.14 Aug 15, 2026
Clears every package carrying unreleased user-facing work since 0.7.50.

core adds refreshPage, which re-renders the current url on the server and
applies it in place with no reload, no history entry and no scroll, and
prefetches a link that drives a frame in that frame's own dimension so the
click costs no round trip. The fix records a same-document history entry
before the swap rather than after, which is what made an iOS swipe-back
preview the page the user was already on.

server stops a dev edit to a page or layout reloading the browser, so hydrated
state and scroll survive a save, and marks a sliced frame response so the
client can tell a real subtree from a whole document. The fixes render an
error boundary inside its own layout chain, coalesce a burst of dev reload
signals so rapid edits stop leaving the page unstyled, and root the vendor
specifier scan in the module graph.

ui takes the a11y fix alone.

Three packages are deliberately absent. cli, mcp and intellisense carry no
user-facing change in the range. cli's only such commit was #1414, which #1417
reverted in full, so what remains is the doctor barrel split, an internal move
with an unchanged export surface. mcp picked up three doc-string edits from
the same refactor, naming the new sibling-directory paths its `source` tool can
read, and the paths it already documents still resolve because they are
barrels. intellisense picked up nothing at all.

Raises packages/server's declared @webjsdev/core range from ^0.7.50 to
^0.7.51. The dev refresh reads refreshPage through a runtime feature check
rather than a static import, so nothing breaks without it, but the release PR
is the only place that bump is legal and core carries the earliest date in the
batch so it publishes first.

core and server carry the generated notes verbatim. ui is edited twice, both
because the generator reads conventional-commit prefixes and cannot see
anything else. It wrote #1414 into the entry for work #1417 has since reverted,
which is removed along with the Features section it emptied; and its excerpt is
the first lines of a squashed message, which for #1412 opened on the CDP
measurement instrument rather than on the fix, so the fix sub-commit takes its
place.
@vivek7405
vivek7405 force-pushed the chore/release-2026-08-15 branch from 8a2f251 to 4b86abd Compare August 15, 2026 05:46
@vivek7405
vivek7405 merged commit b15bbb4 into main Aug 15, 2026
10 checks passed
@vivek7405
vivek7405 deleted the chore/release-2026-08-15 branch August 15, 2026 05:49
@vivek7405 vivek7405 mentioned this pull request Aug 15, 2026
4 tasks
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