Release ARSAS 1.6.29

[masarray]

Release scope

Publish ARSAS 1.6.29 from the current validated main after the ARIEC61850 reconciliation/DataSet integration and final signal-inventory recovery work.

Included since v1.6.28

• consume ARIEC61850-owned DataSet semantic bindings without app-side IEC heuristics (Integrate ARIEC61850 DataSet bindings without app-side IEC heuristics #169);
• integrate connected design/live reconciliation, authoritative Absent handling, existing-session probing, COMTRADE/FileOpen interoperability through the pinned ARIEC Make IED capability actions clear and compact #71 baseline, and Explorer/FAT UX refinements (Consume ARIEC reconciliation status in FAT live binding #170);
• synchronize stale Pages release-note evidence for the already-published 1.6.28 website state (Fix stale Pages release-note evidence for v1.6.28 #171);
• restore every ARIEC-declared mandatory primary static DataSet signal to Signal Selection inventory without forcing user selection, app-side reference canonicalization, or false read-success state (Restore all mandatory IED DataSet signals in selection wizard #172).

Release metadata

• version: 1.6.29
• channel: stable
• platform: Windows x64
• publicationRequest: 17
• primary public asset: ARSAS-Windows-x64-Setup.exe

Architecture boundary

ARIEC61850 remains authoritative for IEC 61850 model/DataSet semantics, reference canonicalization, reconciliation and MMS protocol verdicts. ARSAS owns application workflow, inventory/UI projection, lifecycle and evidence presentation.

Release-documentation hardening

Final review caught that bumping only the four canonical version files would leave landing/release-notes.json at 1.6.28 and could intentionally fail the Pages version-consistency gate. This PR therefore also advances the public bilingual release notes to 1.6.29 in the same atomic release change, avoiding a repeat of the stale-site repair needed after the previous release.

Publication gate

The release diff is limited to the four canonical version files plus landing/release-notes.json. Merge only after CI is green on the exact final head and main is rechecked against the release branch base. Merging .release/windows.json into main intentionally triggers the official release-windows.yml pipeline, which rebuilds/tests the exact release source, smoke-tests portable and installer packages, validates checksums/SBOM/provenance, attests artifacts, and publishes the GitHub Release. sync-release-documentation.yml then waits for the published release and synchronizes exact public hashes/size/provenance evidence.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5a6ae1b9e1

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".