Repository navigation
feat(v1.55.0): add remove-relations-compatibility-config codemod - #162
Conversation
|
Review-blocked: current transform selects YAML keys with root-text regex/indentation parsing rather than parser-backed YAML path traversal. This can miss valid mapping forms/indentation and violates issue #150 detection requirements. PR kept draft pending correction, fixtures, and fresh review; do not merge yet. |
|
Fresh corrected review still blocks readiness: flow-mapping edits rebuild from pair text and may drop unrelated YAML comments between pairs. Add red fixtures for flow |
|
Final review at 37421a3 remains blocked: empty |
|
Fresh actual-diff review at 1b5d388 found another P1: flow-style |
…elations-compatibility-config # Conflicts: # README.md
Summary
Independent internal review signed off on HEAD f3be127: AST path and fixture coverage reviewed; 16/16 fixtures and workflow validation passed, with no P1/P2 blockers. PR is ready for review; no formal GitHub review has been submitted.
Closes #150
Evidence
Before (red): new fixture failed, proving prior data-loss path in flow root mapping
After (green): fixture and full package suite pass
Repo checks:
Performance audit (workflow path, selective app-config globs):
Approved clean-source QA (read-only)
0863f0349c63fa7475b89aed71b6fb8214791394: rc=0 (~4s), zero directcatalog.enableRelationsCompatibilitykeys among 7 tracked app-config YAMLs, zero edits; source SHA/status unchanged.4c760a005dd582df1a61aec39ae50ad565f6dbbc: rc=0 (~4s), zero target keys among 110 tracked app-config YAMLs, zero edits; source SHA/status unchanged. Original dirty checkout untouched.Merge Danger
Door: two-way
Codemod package-only changes + fixtures + generated README index update; revert is a normal git revert.
Blast Radius: low
Scope limited to
@backstage/remove-relations-compatibility-configYAML transform behavior and docs index ordering; no runtime app/library behavior changes.