Skip to content

train: 0.8.0 release candidate (alpha.16) - #372

Merged
andersalm merged 444 commits into
developfrom
release/train-0.8.0-rc3
Oct 14, 2026
Merged

andersalm merged 444 commits into
developfrom
release/train-0.8.0-rc3

Conversation

@andersalm

Copy link
Copy Markdown
Contributor

0.8.0 release train (RC alpha.16), built on develop aa3d61e. One merge commit per reviewed head, in this order:

Merged Head Review
#359 prepare fail-fast 598977c PASS
#360 upstream fetch retry 46272d8 PASS
#361 update from current + "install command needed" message (fix/update-skip-safe) 3d5a10c PASS
#351 dependency advisories (+ quinn-proto 0.11.19, RUSTSEC-2026-0338..0343) 983c409 PASS
#353 per-capsule signed records (includes #277) 955e37c PASS
#335 stable release mode 07da061 PASS
#338 sign-in errors + second passkey (OMP fallback) 8e8ba68 PASS
#336 ticket addresses 26d6784 PASS
Community release pin (maintainer-signed network file; test Homes isolated) ea20fb0 PASS
#348 Local AI 4096a19 PASS
Release text (CHANGELOG, OVERVIEW) b62a474 PASS
#309 Community Chat (includes #116), rebuilt UI assets + 3 test fixes f173210 PASS

Train-only commits: ef0b11d, 854eff9, 04016de (record admission before the installer message), c2145d3 (#348 test construction). Integration review PASS on 04016de and c2145d3.
The component PRs are closed with a link to this PR after it merges.

Load current Room state and expire its view without rewriting nine store files. Validate the current token and room access on every read.

Verified: configured poll store bytes/inodes/mtime and current expiry/access/session regressions; existing verified projection/scoping tests; Clippy and format gates.
Fresh navigation hints still advance their replay guard. Save changed selectors and explicit clears once while repeated settled hints preserve Home state.

Verified: existing Home regression through four actual selectors and fresh restore, unchanged hint replay/loading/clear checks, navigation consumers and product data entropy gate.
A timestamp one second outside the allowed future window can become valid while the full parallel suite signs and verifies it. Keep the future fixture beyond that window without changing Runtime admission.

Verified: independent source analysis, formatting and data entropy gates. The normal pre-push gate runs the complete current server suite before publication; failed b7 proof remains retained.
Integrate alpha.12 develop 8941d47 with the reviewed Chat batch. Preserve the Unreleased Chat notes and published alpha.12 notes as separate entries. Carrier code merged automatically; no Chat authority, delivery or selection fix changed.

Verified: clean conflict resolution, product data gate, workspace and chain-provider formatting. The complete combined-source gate runs before publication.
Reuse one freshly verified Profile and one protected contact snapshot for presentation. Preserve fresh seed, signer, chain and scope checks; send and mutation authority still load their own current evidence.

Independent source review and product-data, diff and formatting checks pass. Native compilation and the installed CPU measurement remain pending until the disk reserve is restored.
Keep at most 512 successful public-key, signature and domain-digest tuples. The canonical retained-receipt regression covers the measured working set while current trust, grants, expiry and revocation stay with callers.

Independent source review and product-data, diff and formatting checks pass. Native compilation and the installed CPU measurement remain pending until the disk reserve is restored.
…lity

# Conflicts:
#	elastos/CHANGELOG.md
#	elastos/crates/elastos-server/src/carrier.rs
…e load (#339)

The capsule posts home-agent:ready after its workspace loads; when that beat
the iframe load event, the load handler cleared is-ready and the room stayed
black. Count readies and loads per launch and reset only when a load has no
ready of its own (a real capsule document reload).
…lo nonce (#339)

Replaces the ready/load counters from bc41a79, which drifted after a
failed load and could not tell which document sent a delayed ready. Home
sends home-agent:hello {nonce} after each frame load and shows the room only
for the ready that echoes the current nonce; the Assistant answers a hello
once its workspace has loaded. The contract lives in
home-agent-message-contract.js and home-agent-shell-smoke covers ready before
load, load before ready, a failed load then a good reload, and a delayed
ready from the replaced document.
…nded wait (#339)

After Undo with the Home tab open, the new shell meets an earlier Assistant
that ignores hello and sends a nonce-less ready. That ready now counts for
the load it belongs to (before or after the load event; a later load resets
it), while current Assistants still must echo the hello nonce. A load that
no ready answers within 5 s shows the room anyway instead of staying black.
…ready (#339)

Readiness no longer depends on the iframe load event. Each Assistant
document posts hello {docId} when its script starts and ready {docId} after
its workspace loads; Home hides on a hello, shows once on the ready from the
current document, ignores readies from any other document, and resets before
it sets the frame src. An earlier Assistant (after Undo) sends only {type}
ready, which shows the room as before. Removes the load-event reset, the
hello nonce and the 5 s recovery.
…339)

The contract behaviour cases cover readiness; the source check pinned text.
After Undo with Home open, an in-frame reload into the earlier Assistant
sends only {type} ready while a current docId is still recorded; it was
ignored and the room got no open or handover. A {type}-only ready now means a
legacy document is active: clear the current docId and show the room; a later
hello from a current document takes over again.
…read (#339)

Home can send open or shelf-handover to a new Assistant document early (a
stale ready from the document it replaced reaches Home first; contentWindow
is the same WindowProxy). Raising the room and focusing the composer then let
the workspace snapshot overwrite typed text. The Assistant now holds the
latest open and handover (a close drops them) with the composer read-only
until its workspace initialization completes, then applies them once.
The port test now picks an IPv6/IPv4 port pair whose IPv4 side is free
(up to 20 attempts) instead of assuming it. The DM restart test polls
retry_pending for up to 30 s while transport is unavailable instead of a
fixed 2 s pause; retries resend the same durable envelope, and the
existing one-record / one-incoming assertions are unchanged.
Workspace version 0.8.0 in elastos/Cargo.toml; the Runtime lock file and the
15 capsule lock files that pin Runtime crates move with it (66 version lines,
elastos-* crates only; no other dependency changes; cargo metadata --locked
--offline passes in all 34 workspaces). The carrier dependency check expects
elastos-identity 0.8.0.
The user-facing bullets move from [Unreleased] into [0.8.0] - 2026-10-13, and
the same bullets go under [0.8.0-alpha.16], the release candidate built from
the same source. [Unreleased] keeps the developer detail. Both sections pass
changelog_changes and the signer's check_release_changes (12 bullets, at most
449 bytes, 2560 bytes in total).
…tant room (#339)

Restoration awaits each saved window's launch; when the person opened the
Assistant meanwhile, restoring the saved Space ran syncAgentSpaceToActiveStage
and closed the room. Restoration now leaves the Space alone while the Agent
room is open or opening (face up or mid-morph, or the ring on the Agent
Space). The installed journey records Assistant opening as open_assistant.
…s an opening room (#339)

The guarded return skipped presentation sync, so if the room closed before
the ring entered Agent, windows restored to another Desktop showed on the
current one. Sync stage presentation before keeping the current Space.
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.

2 participants