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.

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:

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

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

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

Fixes

Many fixes shipped on this line. The classes that recur are worth naming because each now has a guard: