Skip to content
YSoNet

v2026.9.1 release notes

Highlights

Section titled “Highlights”

Compared with v2026.8.1, this release improves everyday console use and corrects DataContractSerializer output:

  • PowerShell completion setup handles paths with spaces or apostrophes. Policy probes have a timeout, and profile access errors are reported rather than silently treated as an absent profile. See completion setup.
  • The wizard restores the console's original QuickEdit setting when you leave it.
  • TextFormattingRunProperties with DataContractSerializer and --hasRootDCS keeps the intended type inside the root wrapper.
  • The research archive now provides matching English Markdown/PDF paths and separate reports for missing documents, pending review, and missing source bytes.

These notes were added on 2026-09-25 for the already published v2026.9.1 release. They describe revision 98fc35a72be1e7af52ec56be6d126a69ee2bfb6a relative to 86399e4, the v2026.8.1 release revision.

Compatibility and upgrade

Section titled “Compatibility and upgrade”
  • Extract the whole release ZIP into a fresh folder; do not replace only the EXE. Windows and .NET Framework 4.7.2 or newer 4.x remain required.
  • TextFormattingRunProperties --hasRootDCS is now refused with formatters other than DataContractSerializer. Select that formatter or omit the option.
  • XamlTypeConverterFetch listings now display (2) for each supported formatter to indicate two variants. The suffix is descriptive, not part of the -f value.
  • Saved local research links under docs/references-md/ need updating to docs/archived-references/. Use the archive index to find the Markdown/PDF pair.
  • If completion is already installed, review completion status. Setup failures now return nonzero when a profile cannot be read or changed.

The quick reference and archive-free checkout are documentation added after publication; they are not new executable features in this release.

Known limitations

Section titled “Known limitations”
  • In this published release, some incomplete commands print diagnostics to stdout and exit 0. Later source fixes do not change this ZIP; check output as well as exit status when scripting this version.
  • Native Linux/macOS execution is not established. Use the Windows VM or WSL workflow.
  • A runtime listed in gadget metadata is recorded evidence, not a guarantee for every application. An omitted version is not proof of incompatibility.
  • Published archive files can still have completeness or review gaps; read the archive's separate reports rather than inferring completeness from a file's presence.

Validation

Section titled “Validation”

At publication, the release workflow built Release and checked packaging, shipped test-host probes, and executable string hiding. It did not run NORMAL or FULL. Later workflow changes do not retroactively validate that published ZIP.

During the 2026-09-25 documentation review, the published ZIP was downloaded and extracted, help and wizard startup/quit were checked, and selected generation, encoding, and migration commands were exercised on Windows with .NET Framework 4.8.1. No payload was deserialized or executed during those checks.

NORMAL and FULL were not run for this review; there is no ENVIRONMENT VERDICT from those suites to report. The source changes above were reviewed, but these smoke checks are not validation of every formatter, plugin, runtime, or target.