chores(x2a): bump all dependencies to match RHDH 1.9.3#2655
Merged
eloycoto merged 1 commit intoredhat-developer:mainfrom Apr 5, 2026
Merged
chores(x2a): bump all dependencies to match RHDH 1.9.3#2655eloycoto merged 1 commit intoredhat-developer:mainfrom
eloycoto merged 1 commit intoredhat-developer:mainfrom
Conversation
|
Important This PR includes changes that affect public-facing API. Please ensure you are adding/updating documentation for new features or behavior. Changed Packages
|
Review Summary by QodoUpgrade x2a plugin dependencies to RHDH 1.9.3
WalkthroughsDescription• Upgrade all x2a plugin dependencies to align with RHDH 1.9.3 • Update supported Backstage versions from 1.42.0 to 1.45.0 • Bump Backstage core packages to latest compatible versions • Simplify root package.json resolutions, removing outdated pins Diagramflowchart LR
A["x2a Workspace"] -- "version bump" --> B["1.45.3"]
A -- "supported-versions update" --> C["1.45.0"]
A -- "dependency upgrades" --> D["Backstage 1.9.3 packages"]
D -- "includes" --> E["core-plugin-api 1.12.0"]
D -- "includes" --> F["backend-defaults 0.13.1"]
D -- "includes" --> G["plugin packages updates"]
File Changes1. workspaces/x2a/.changeset/chatty-aliens-pay.md
|
Code Review by Qodo
1. Backstage API version mismatch
|
![rhdh-qodo-merge[bot]](https://avatars.githubusercontent.com/in/1961108?s=60&v=4){kind=small}
Comment on lines
29
to
32
| "@backstage/plugin-auth-backend-module-bitbucket-provider": "^0.3.9", | ||
| "@backstage/plugin-auth-backend-module-github-provider": "^0.3.9", | ||
| "@backstage/plugin-auth-backend-module-gitlab-provider": "^0.3.9", | ||
| "@backstage/plugin-auth-backend-module-guest-provider": "^0.2.14", |
There was a problem hiding this comment.
1. Backstage api version mismatch 🐞 Bug ☼ Reliability
The x2a workspace forces @backstage/backend-plugin-api to 1.5.0, but the resolved versions of some backend packages (e.g. Bitbucket auth module and permission backend) declare dependencies on newer @backstage/backend-plugin-api ranges, meaning they may execute against an API they were not built for. This can break backend startup at runtime when those packages call APIs added after 1.5.0.
Agent Prompt
### Issue description
`@backstage/backend-plugin-api` is forced to 1.5.0, but the resolved versions of some Backstage backend packages in `yarn.lock` require newer backend-plugin-api ranges (e.g. `^1.8.0` / `^1.6.2`). This creates a semver-incompatible override that can lead to runtime failures.
### Issue Context
- `workspaces/x2a/package.json` uses `resolutions` to pin `@backstage/backend-plugin-api`.
- `workspaces/x2a/yarn.lock` currently resolves:
- `@backstage/plugin-auth-backend-module-bitbucket-provider@^0.3.9` -> 0.3.13, requiring `@backstage/backend-plugin-api: ^1.8.0`
- `@backstage/plugin-permission-backend@^0.7.3` -> 0.7.8, requiring `@backstage/backend-plugin-api: ^1.6.2`
- `@backstage/backend-plugin-api` -> 1.5.0
### Fix Focus Areas
- Decide which version set is correct for “RHDH 1.9.3” and make it consistent:
- Either bump the pinned `@backstage/backend-plugin-api` (and any other Backstage packages) to satisfy the newer requirements,
- OR pin the offending packages (`@backstage/plugin-auth-backend-module-bitbucket-provider`, `@backstage/plugin-permission-backend`, etc.) to versions that depend on `@backstage/backend-plugin-api` 1.5.0.
- After choosing the consistent set, regenerate `workspaces/x2a/yarn.lock` so `yarn install --immutable` passes.
Fix focus areas (edit these files/regions):
- workspaces/x2a/package.json[55-59]
- workspaces/x2a/packages/backend/package.json[23-44]
- workspaces/x2a/yarn.lock[2280-2282]
- workspaces/x2a/yarn.lock[3257-3266]
- workspaces/x2a/yarn.lock[4010-4019]
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
Signed-off-by: Marek Libra <marek.libra@gmail.com>
mareklibra
force-pushed
the
FLPATH-3506.upgradeToRHDH19
branch
from
dfce21e to
dfe93a1
Compare
|
eloycoto
approved these changes
Apr 5, 2026
This was referenced Apr 17, 2026
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
2 participants
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.
Fixes: FLPATH-3506