Conversation
This was referenced Sep 26, 2026
Owner
Author
Owner
Author
|
Superseded by consolidated PR #416, merged to |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
Make the Legacy SAS RCB export guard deterministic and consistent with the application engine dependency, rather than cloning the moving upstream
mainbranch.Root cause and change
The existing guard read the engine from
masarray/ARIEC61850@main, while ARSAS builds againstengines/ARIEC61850.lock.json. A later unrelated engine commit could change this guard's result for an unchanged ARSAS candidate.Preflight and scope
Base:
9d081f54fc6466d13c099e8a94a020c487a36703; head:2dd0c8d20b88ee6a5f6b43688c646c24a117b6d9. Exactly one workflow YAML changed, 20 additions / 2 deletions. Verified every one of the six engine source files and every required engine-source text contract currently checked byscripts/verify-rcb-export.ps1is present at the locked ARIEC61850 commit648124097621046f5f127ceb1cf853fea54db730. The script itself, app source, engine lock, reporting and release paths are unchanged.Validation
This is separate from maintainability PRs #413 and #414 and SCL PR #374. Tracks #380.