Skip to content

Fix SCL mismatch clipping and prepare v1.4.0 stable public release - #44

Merged
masarray merged 8 commits into
mainfrom
fix/scl-readable-stable-release-20261018
Oct 18, 2026
Merged

masarray merged 8 commits into
mainfrom
fix/scl-readable-stable-release-20261018

Conversation

@masarray

Copy link
Copy Markdown
Owner

Operator repair

  • Natural-height SCL binding rows and sufficient status badge width for MISMATCH and other verdicts; score remains accessible on hover without repeating clutter on every row.
  • Wrapping of expected/observed svID in constrained Grid cells (not unconstrained StackPanel), no arbitrary character truncation; reduce the binding matrix to Status, Expected svID, Observed svID, Difference. Typed dataset and full evidence preserved in inspector.
  • Remove redundant SCL caption, verification label, and technical acronym line that duplicates dataset columns.

Stable release preparation

  • Set proper 1.4.0 version (optional suffix remains supported for future betas), update README and publish release notes docs/RELEASE_NOTES_v1.4.0.md.
  • Stable describes the packaged software—not certified IEC 61850 timing, protection operation or metrology. Existing hardware/DPI acceptance limitations remain clearly disclosed.

Gates

  • .NET Windows Release build + regression tests
  • Runtime stability / architecture gates
  • CodeQL and dependency review
  • Portable win-x64 candidate, SHA256 manifest verification
  • Public stable v1.4.0 GitHub Release only once all gates pass.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 18, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-18T01:15:46.806861Z df1a3e7 PR opened
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@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: df1a3e771f

ℹ️ 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 Directory.Build.props
Comment on lines 13 to +14
<VersionPrefix Condition="'$(VersionPrefix)' == ''">1.4.0</VersionPrefix>
<VersionSuffix Condition="'$(VersionSuffix)' == ''">beta.2</VersionSuffix>
<Version Condition="'$(Version)' == ''">$(VersionPrefix)-$(VersionSuffix)</Version>
<VersionSuffix Condition="'$(VersionSuffix)' == ''"></VersionSuffix>

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 Synchronize release metadata with the stable version

Changing the repository version to 1.4.0 makes the repository-health step in .github/workflows/ci.yml fail deterministically because docs/index.html still declares 1.4.0-beta.2 and the README still uses the beta.2 package name; the release workflow also defaults to beta.2 and marks manual releases as prereleases. Update these required version consumers together so CI can pass and the stable workflow cannot publish the old beta package.

AGENTS.md reference: AGENTS.md:L71-L72

Useful? React with 👍 / 👎.

</DataGridTemplateColumn.CellTemplate>
</DataGridTemplateColumn>
<DataGridTemplateColumn Header="Expected" Width="1.25*">
<DataGridTemplateColumn Header="Expected svID" Width="1.2*">

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Preserve protocol identity in the mixed binding matrix

SclFilteredBindingMatrix contains both SV and GOOSE rows, but this change removes the Protocol column and labels every expected identity as an svID. When GOOSE bindings are present, their goID/GoCBRef values therefore appear under an incorrect svID heading and operators can no longer distinguish otherwise similar SV and GOOSE rows; retain the protocol column or use protocol-neutral/dynamic identity headings.

Useful? React with 👍 / 👎.

@masarray
masarray merged commit d138457 into main Oct 18, 2026
7 checks passed
@masarray
masarray deleted the fix/scl-readable-stable-release-20261018 branch October 18, 2026 01:21
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