Repository navigation
[Release] Make CI gates explicit and document the migration - #54
Conversation
2195b39 to
d951b53
Compare
d951b53 to
379e18d
Compare
raorjun
left a comment
There was a problem hiding this comment.
PR CI still does not run most of the new Python tests in this stack. The release gate that does run them is manual and has not run on any review branch. The migration guide gives no modifier map, and BobSim drops unknown keys with no error.
# Conflicts: # CHANGELOG.md
|
Fixed in three commits: e59f38f runs the release gate on |
Purpose
Make release failures attributable to a specific check and document the public API migration.
Approach
Separate translation, initialization, physics, signal, FMU and component checks into named workflow steps and retain their reports. Add mirrored-fixture profiling to CI and update the user guide, migration notes and release-readiness documentation.
Validation
Every workflow target and referenced file was checked. Complete numerical regression and rendered-diagram acceptance remain release gates; a green default CI run does not certify a release.