MeshWeaver 3.1.0
Support lifetime
MeshWeaver 3.x is based on .NET 10 LTS. Its support ends on November 14, 2028, matching Microsoft's published .NET 10 lifecycle. Official 3.x release artifacts are retained throughout that support period. See the Release Support Policy.
3.1.0 is the 3.x line's second release. It is one sealed continuous build of the 3.1 line,
3.1.<run>, given its clean name; nothing was rebuilt to make it. It covers what merged
after 3.0.0 until the 3.x line was split off onto its own branch.
Two lines: 3.x and 4.x
Each platform major is now a separate delivery line (policy
major-lines-run-separately). The default branch builds the
4.x line on .NET 11, and the 3.x line continues on its own branch on .NET 10. Each line
promotes, seals and labels its own image sets, and a 3.x release is promoted from the 3.x line.
An installation's update pattern names its major (3.*), so a 3.x installation keeps receiving
3.x builds until its pattern is changed. See Major Lines Run Separately.
Versioning: every build is a release version
Every continuous build is a plain SemVer version 3.1.<run>. The -ci.<n> notation is
retired, so a build and a release order the same way for every reader. Compiled module bytes are
keyed on a platform compatibility epoch rather than on each build's identity, so a platform roll
no longer recompiles content that did not change. A platform roll also no longer waits for a
plugin seal, and only a declared break holds it.
Modules update live
Every module runs in its own collectible load context. Module endpoints, view packs, root services and the builder hook update while the portal keeps running, and only boot-time infrastructure may ask for a restart. A module can be reloaded, and it is uninstalled in two phases. Packages update automatically, independently of the platform's seal. A NodeType recycle cascades through its dependency network in one request, and a cold address instantiates nothing.
- Live module update · Module reload · Stale state until recycle
- Dependency graph — static, dynamic and declared edges
Views bind data instead of baking it
The default node page, the NodeType pages, the Settings tabs, the plugin catalog and the sample views are now templates. A view renders its shape at once and binds its data afterwards, so it no longer waits on a read before it can draw. A click inside a bound row carries its row. A button shows that its action is pending and confirms when the action is done. The code and diff editors bind directly to a node field.
A wider platform control set
Pages are composed from platform controls instead of hand-built markup:
- design tokens generated from the accent colour, and one palette engine for charts and icon plates: Design tokens · Colour palettes
- a chip bar, breadcrumb and field strip shared by every app, and a catalog app over mesh search, with a table mode and server-side sorting: Chip bar · Catalog app · Mesh search
- UML class diagrams projected from content schemas, waterfall and hierarchy figures: UML class diagrams · Waterfall · Hierarchy
- image, embed, divider, message bar, link, QR code, share link, install-app and audio controls, plus a tile-flow layout: Message bar and link
Home, inbox and profile
The app directory is the default home: a message box, then Apps, then Spaces, with a getting-started guide. Tiles are declared as data, and an admin-only tile shows only to global admins. The inbox brings activities, approvals, chats and mail together in one data-bound list. It supports multi-select, Delete with Undo, filters per source and per state, triage tags and sanitised mail rendering, and it reads several mailboxes per person through opt-in mail copies. Each app has its own notification settings, and a person has a real profile page.
Querying the mesh
The query language has grammar, schema and semantic autocomplete. Exact-name and Space matches
rank first in free-text search. sort:subtreeLastModified orders containers by their newest
descendant. An answer reports when it used a weaker method, and a filter-only query clips newest
first.
Identity and access
- Account lockout: a locked person holds nothing, and unlocking gives everything back. See Account lockout.
- Scoped API tokens and service identities: non-person principals with tokens of their own. See Service identities.
- Approval step-up with a passkey, TOTP or Entra ID rung and a sealed single-use receipt. See Approval step-up.
- Stamped fields: only a node's own hub writes a field its type declares stamped. See Stamped fields.
- Closed to anonymous callers on request: an instance-level switch closes a mesh to logged-out callers.
- Secrets entered write-only in the portal: the portal accepts secret values and never shows them back, through sealed secret envelopes. See Instance secrets.
- One redaction point: one point redacts sensitive data in every log and egress rendering. See Sensitive content in logs.
- Governed broad grants: a broad grant is issued only through a governed activity. A node type can declare a point read and type-scoped grant rules. See Granting access.
Read verdicts were also tightened in many places. A query follows grant changes while it is open. A read delivers its emissions as the reader. A satellite applies every policy between itself and its main node. An API token's principal is bound to the caller that writes it.
Operating an installation
- Signed control lane: the control instance acts on another instance's mesh through a signed lane, and the operator's actions are governed. These actions are reboot, database migration as its own job, dump analysis, inventory, storage prune and cluster upgrade. See Control lane · Instance reboot.
- Planned database migrations: a release states the schema version it expects, and the operator migrates first. See Database migration procedure.
- Provisioning: each instance's database is its own release, an instance asks for its TLS certificate while it is provisioned, and a provisioned instance runs a first-run setup. See Instance identity and setup.
- Build infrastructure: standing build hosts, a control-owned shared artifact store, and self-hosted OCR and model services. See Shared artifact store · OCR service · Local model service.
- Messaging: streamed responses, the Communication Hub with open vocabularies, and durable streams saved as mesh nodes. See Communication Hub · Durable streams.
Security
Every release is scanned with OWASP ZAP against the deployment serving the candidate build, in two runs: a public active scan and an authenticated passive baseline (OWASP ZAP Scan — Every Release).
For 3.1.0, both scans are PENDING. Neither run has been recorded yet, so this page reports no
verdict. The authenticated run needs a person to sign in with a real browser session. When both
runs are done, this section will carry their verdict lines and the disposition of every finding.
The v3.1.0 tag is not pushed before then.
Upgrading from 3.0.0
- Nothing to do for a running 3.x installation. It keeps rolling forward on the 3.x line,
and a Stable installation takes
3.1.0as its next release. - Module floors are satisfied. A module that declares a 3.0 floor runs on 3.1. The floor is judged as a regression check, never absolutely (Release gates).
- Continuous build tags changed shape. A pin or script that matched
3.1.0-ci.<n>must match3.1.<run>.
Fixes
Many fixes shipped on this line. The classes that recur are worth naming because each now has a guard:
- access verdicts that did not follow a grant change while a query or stream stayed open;
- pages that waited on a read before they rendered, which templates now prevent;
- module identity churn that recompiled unchanged content;
- deliveries that outlived the hub that should have answered them.