Skip to content
YSoNet

v2026.9.2 release notes

Highlights

Section titled “Highlights”

Compared with v2026.9.1, this release improves discovery, scripting, and release verification:

  • Compact help and clearer wizard settings make options easier to find.
  • doctor checks an installation without running payloads. The JSON catalog provides structured metadata and a versioned schema for integrations.
  • The documentation website adds searchable guides and module references, with light and dark themes. Pages are generated from the repository docs and public CLI metadata.
  • Release downloads include checksums, signed build provenance, component inventory, and runtime observations. See release verification.

Compatibility and upgrade

Section titled “Compatibility and upgrade”

Extract the entire ZIP into a fresh folder. Windows and .NET Framework 4.7.2 or newer 4.x remain required; native Linux/macOS execution is not established.

Scripts must check the exit code: invalid or incomplete one-shot commands and failed writes now exit nonzero. Diagnostics go to stderr; requested data goes to stdout or --outputpath. Successful formatter searches exit zero. Help is now compact; use --fullhelp for the exhaustive reference or --list catalog for structured discovery. Existing name/value listings retain their line-based format.

Known limitations

Section titled “Known limitations”

Catalog declarations are not execution results or guarantees about a target. Runtime reports distinguish observed outcomes from unverified cells. A green test tier does not establish every module, formatter, runtime, or target combination. The website follows current source and may describe changes newer than a download.

Validation

Section titled “Validation”

Pre-publication CI tested source e57f3bd905ffdc8edea64b5952043693a3e48452: Debug NORMAL and extracted Release NORMAL each reported 557 passed, 0 failed, 0 environment-skipped, with ENVIRONMENT VERDICT: clean. The Release documentation checks also passed. That run did not execute FULL.

Publication requires fresh Debug NORMAL and packaged Release FULL on the release commit. The attached test-results.md records their actual totals, environment verdicts, and unverified cells; build-provenance.json identifies the tested source and ZIP. The separate OOB, DoS, LEGACY, and NET40 tiers are not publication gates and were not run by the CI above.