Skip to content

release: ARSAS 1.6.35 - #277

Merged
masarray merged 4 commits into
mainfrom
release/v1.6.35
Sep 8, 2026
Merged

masarray merged 4 commits into
mainfrom
release/v1.6.35

Conversation

@masarray

@masarray masarray commented Sep 8, 2026

Copy link
Copy Markdown
Owner

Release candidate

ARSAS 1.6.35 is cut from current main after merged PR #274.

Included accepted field fixes:

  • black IED fascia from Assets/black-fascia-ied.svg
  • LED state follows Engineering monitoring state: LIVE green, first Stop red
  • Engineering -> FAT progress restoration for the same SCL content
  • Legacy SAS multi-RCB selections persist across DataGrid scrolling/virtualization

Release metadata only

This PR changes only the canonical version metadata and .release/windows.json publication request. No runtime source, ARIEC61850 pin, protocol stack, acquisition path, control backend, or UX code is changed here.

Safety

The runtime candidate was already validated at PR #274 head 7508d303a96baa947e17a16d2f319414e79e8042 with Build #2187, IO #1049, SV #1273, regression tests, portable publish, and smoke-test all green. This release PR is intentionally based on main after that merge so it cannot omit those accepted changes.

Target version: 1.6.35.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 80ce17742d

ℹ️ 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".

Comment thread .release/windows.json
@@ -1,7 +1,7 @@
{
"version": "1.6.34",
"version": "1.6.35",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Add matching release notes before requesting publication

When this reaches main, changing this manifest triggers both release-windows.yml and sync-release-documentation.yml: the former marks v1.6.35 as the latest release, while the latter writes 1.6.35 evidence to landing/latest.json; however, landing/release-notes.json is still version 1.6.33. The subsequent pages.yml deployment explicitly rejects differing evidence and notes versions, leaving the public site on old checksums while its releases/latest/download links resolve to the new 1.6.35 binaries. Include matching 1.6.35 release-note metadata before triggering publication.

Useful? React with 👍 / 👎.

@masarray
masarray merged commit 4ebd559 into main Sep 8, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant