redhat-developer / redhat-developer/rhdh-plugin-export-overlays
[RHDH 2.1.0] Backstage 1.54.0 compatibility: extensions
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 9
- Forks
- 72
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 143
Description
Backstage version bump — action needed
RHDH 2.1.0 is targeting Backstage 1.54.0.
The extensions workspace is currently on Backstage 1.52.1.
What you need to do
- Update your plugin in the upstream repository to be compatible with Backstage 1.54.0
- Once updated, the daily update workflow will automatically create a PR in this repo to update the workspace reference
- Alternatively, you can trigger the update workflow yourself. See https://github.com/redhat-developer/rhdh-plugin-export-overlays/wiki/Metadata-Synchronization#automated-synchronization for more:
Timeline
| Milestone | Date |
|---|---|
| Feature freeze | 2026-09-22 |
Details
| Field | Value |
|---|---|
| Workspace | workspaces/extensions |
| Upstream repo | https://github.com/redhat-developer/rhdh-plugins |
| Current Backstage version | 1.52.1 |
| Target Backstage version | 1.54.0 |
Resources
cc @redhat-developer/rhdh-ui, @redhat-developer/rhdh-plugins
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the workspaces/extensions workspace and the upstream rhdh-plugins repository, then read the linked plugin-owner responsibilities and version-updates guides. Check the update-plugins-repo-refs.yaml workflow to understand synchronization; done means the upstream plugin supports Backstage 1.54.0 and the workspace reference is updated by the workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100