Repository navigation
Fix SCL mismatch clipping and prepare v1.4.0 stable public release - #44
Conversation
…remove repeated metadata
…certification boundaries
…vidence boundaries
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 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".
| <VersionPrefix Condition="'$(VersionPrefix)' == ''">1.4.0</VersionPrefix> | ||
| <VersionSuffix Condition="'$(VersionSuffix)' == ''">beta.2</VersionSuffix> | ||
| <Version Condition="'$(Version)' == ''">$(VersionPrefix)-$(VersionSuffix)</Version> | ||
| <VersionSuffix Condition="'$(VersionSuffix)' == ''"></VersionSuffix> |
There was a problem hiding this comment.
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*"> |
There was a problem hiding this comment.
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 👍 / 👎.
Operator repair
Stable release preparation
docs/RELEASE_NOTES_v1.4.0.md.Gates