Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Bump all @backstage/* packages to the 1.52.0 release line via backstage-cli versions:bump. Also updates: - @red-hat-developer-hub/cli ^1.10.2 -> ^1.11.4 - @red-hat-developer-hub/backstage-plugin-theme ^0.14.0 -> ^0.15.0 - @backstage-community/plugin-rbac-backend 7.12.1 -> 7.16.2 Known issue: yarn tsc fails due to catalogProcessingExtensionPoint moving from @backstage/plugin-catalog-node/alpha to the main export. Fix tracked in a follow-up PR. Generated with Claude Code
Yarn merges multiple version ranges that resolve to the same version into a single line (e.g. "pkg@npm:^3.8.0, pkg@npm:^3.8.1":). The grep pattern expected the range to be the sole key, so it never matched merged lines. Drop the trailing `":` anchor to match the range anywhere in the key line. Generated with Claude Code
In Backstage 1.52.0, catalogProcessingExtensionPoint moved from @backstage/plugin-catalog-node/alpha to the main export. Split the import: catalogProcessingExtensionPoint from the main entry point, catalogModelExtensionPoint stays in /alpha. Generated with Claude Code
1e859d2 to
951afcc
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## main #538 +/- ##
=======================================
Coverage 95.72% 95.72%
=======================================
Files 230 230
Lines 14288 14289 +1
Branches 3852 3852
=======================================
+ Hits 13677 13678 +1
Misses 600 600
Partials 11 11
Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
|



Summary
@backstage/*packages to the 1.52.0 release line viabackstage-cli versions:bump --release 1.52.0@red-hat-developer-hub/cli^1.10.2 -> ^1.11.4@red-hat-developer-hub/backstage-plugin-theme^0.14.0 -> ^0.15.0@backstage-community/plugin-rbac-backend7.12.1 -> 7.16.2check-dependency-pins.sh) reports false FAIL due to a pre-existing grep pattern bug on merged yarn.lock ranges -- fix tracked separately.resolutionsentries (CVE-driven security pins) intentionally unchangedPackages with breaking changes
@backstage/backend-defaults@backstage/plugin-auth-backend@backstage/plugin-auth-node@backstage/plugin-catalog-react@backstage/plugin-permission-react@backstage/plugin-scaffolder-backend@backstage/plugin-scaffolder-react@backstage/uiSignals package version alignment
4 signals-family packages have lower version specifiers than before, matching the Backstage 1.52.0 release manifest. The previous versions were from the 1.53.x line (published after 1.52.0):
@backstage/plugin-signals@backstage/plugin-signals-backend@backstage/plugin-signals-node@backstage/plugin-signals-reactKnown issue
yarn tscfails with 2 errors --catalogProcessingExtensionPointmoved from@backstage/plugin-catalog-node/alphato@backstage/plugin-catalog-node(main export). Fix tracked in a follow-up PR.Upgrade helper: https://backstage.github.io/upgrade-helper/?from=1.49.4&to=1.52.0
Test plan
yarn installpasses (Node 22 and Node 24)yarn test:all-- 186/187 suites pass, 3943/3945 tests pass (2 failures are the catalogProcessingExtensionPoint import issue)yarn tsc-- blocked by follow-up import fix PRGenerated with Claude Code