Update `bulk-import` workspace to commit `dbc4e81` for backstage `1.49.3` on branch `main` by github-actions[bot] · Pull Request #2154 · redhat-developer/rhdh-plugin-export-overlays

github-actions · 2026-04-04T15:16:09Z

Update bulk-import workspace at commit redhat-developer/rhdh-plugins@dbc4e81 for backstage 1.49.3 on branch main.

This PR was created automatically.
Click on the following link to see the source diff it introduces: redhat-developer/rhdh-plugins@8ab71de...dbc4e81.

Before merging, you need to export the workspace dynamic plugins as OCI images,
and if possible test them inside a RHDH instance.

To do so, you can use the /publish instruction in a PR review comment.
This will start a PR check workflow to:

export the workspace plugins as dynamic plugins,
publish them as OCI images
push the oci-images in the GitHub container registry with a PR-specific tag.

…7.3` on branch `main`

openshift-ci · 2026-04-04T15:16:21Z

Hi @github-actions[bot]. Thanks for your PR.

I'm waiting for a redhat-developer member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

github-actions · 2026-04-04T17:32:00Z

Publish workflow has completed with failure.

Publishing process

❌ Plugins with errors during export or container image publishing:

plugins/bulk-import
Published container images:
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-bulk-import-backend:pr_2154__7.2.1

Backstage-incompatible workspaces

Some workspaces have a backstage version (in sources or in their overlay folder) which is incompatible with the target Backstage version (1.48.3).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/bulk-import	1.47.3	⚪	BS Version History

How to fix

You have 3 main options:

Use the already-opened PR : For automatically-discovered workspaces, there might already be an automatically-opened PR that updates the commit to the target backstage version (Automatic PR link in column 4 above): just publish the plugins and test them from the PR by following the PR instructions.
Manually update the workspace commit :
- Find a newer commit, with a backstage version compatible with the target backstage version :__*
  - Backstage version history available: A BS Version History link might be available in column 4: in the workspace source repository, it points to the list of commits touching the backstage.json file. This would help you finding out whether this workspace has a commit that has been published for the target backstage version.
  - No info available: If no information is is provided in column 4, the backstage.json probably does not exist in workspace sources. You would have to look deeper into the newer commits of workspace sources, possibly in the low-level dependencies in the package.json files, to find out a commit with an underlying backstage version compatible with the target backstage version.
- Then, in the overlay repository, update the repo-ref field of the source.json file to the new source commit, and remember to also change the repo-backstage-version field to the corresponding compatible backstage version.
No compatible commit : If the workspace sources contain no compatible newer commit ( == a commit that provides a backstage.json version compatible with the target backstage), but the current workspace commit is known to work with the target backstage version, then you can override the declared backstage version compatibility for this workspace commit in the overlay repository: add a backstage.json file at the root of the overlay workspace folder with the desired target backstage version. This would require full testing of the workspace plugins on the target backstage though.

Metadata Validation

✅ All metadata files validated successfully.

github-actions · 2026-04-08T18:06:58Z

Successfully updated file versions.jsonfrom branch main into this PR in commit a8c4194

github-actions · 2026-04-09T00:17:11Z

Publish workflow has completed with failure.

Publishing process

❌ Plugins with errors during export or container image publishing:

plugins/bulk-import
Published container images:
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-bulk-import-backend:pr_2154__7.2.1

Backstage-incompatible workspaces

Some workspaces have a backstage version (in sources or in their overlay folder) which is incompatible with the target Backstage version (1.48.3).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/bulk-import	1.47.3	⚪	BS Version History

How to fix

You have 3 main options:

Use the already-opened PR : For automatically-discovered workspaces, there might already be an automatically-opened PR that updates the commit to the target backstage version (Automatic PR link in column 4 above): just publish the plugins and test them from the PR by following the PR instructions.
Manually update the workspace commit :
- Find a newer commit, with a backstage version compatible with the target backstage version :__*
  - Backstage version history available: A BS Version History link might be available in column 4: in the workspace source repository, it points to the list of commits touching the backstage.json file. This would help you finding out whether this workspace has a commit that has been published for the target backstage version.
  - No info available: If no information is is provided in column 4, the backstage.json probably does not exist in workspace sources. You would have to look deeper into the newer commits of workspace sources, possibly in the low-level dependencies in the package.json files, to find out a commit with an underlying backstage version compatible with the target backstage version.
- Then, in the overlay repository, update the repo-ref field of the source.json file to the new source commit, and remember to also change the repo-backstage-version field to the corresponding compatible backstage version.
No compatible commit : If the workspace sources contain no compatible newer commit ( == a commit that provides a backstage.json version compatible with the target backstage), but the current workspace commit is known to work with the target backstage version, then you can override the declared backstage version compatibility for this workspace commit in the overlay repository: add a backstage.json file at the root of the overlay workspace folder with the desired target backstage version. This would require full testing of the workspace plugins on the target backstage though.

Metadata Validation

✅ All metadata files validated successfully.

github-actions · 2026-04-09T19:05:14Z

Successfully updated file versions.jsonfrom branch main into this PR in commit b7e8408

github-actions · 2026-04-09T19:16:10Z

Publish workflow has completed with success.

Publishing process

✅ Finished successfully.

Published container images:
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-bulk-import:pr_2154__7.2.1
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-bulk-import-backend:pr_2154__7.2.1

Backstage-incompatible workspaces

Some workspaces have a backstage version (in sources or in their overlay folder) which is incompatible with the target Backstage version (1.48.3).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/bulk-import	1.47.3	⚪	BS Version History

How to fix

You have 3 main options:

Use the already-opened PR : For automatically-discovered workspaces, there might already be an automatically-opened PR that updates the commit to the target backstage version (Automatic PR link in column 4 above): just publish the plugins and test them from the PR by following the PR instructions.
Manually update the workspace commit :
- Find a newer commit, with a backstage version compatible with the target backstage version :__*
  - Backstage version history available: A BS Version History link might be available in column 4: in the workspace source repository, it points to the list of commits touching the backstage.json file. This would help you finding out whether this workspace has a commit that has been published for the target backstage version.
  - No info available: If no information is is provided in column 4, the backstage.json probably does not exist in workspace sources. You would have to look deeper into the newer commits of workspace sources, possibly in the low-level dependencies in the package.json files, to find out a commit with an underlying backstage version compatible with the target backstage version.
- Then, in the overlay repository, update the repo-ref field of the source.json file to the new source commit, and remember to also change the repo-backstage-version field to the corresponding compatible backstage version.
No compatible commit : If the workspace sources contain no compatible newer commit ( == a commit that provides a backstage.json version compatible with the target backstage), but the current workspace commit is known to work with the target backstage version, then you can override the declared backstage version compatibility for this workspace commit in the overlay repository: add a backstage.json file at the root of the overlay workspace folder with the desired target backstage version. This would require full testing of the workspace plugins on the target backstage though.

Metadata Validation

✅ All metadata files validated successfully.

No E2E tests available for this workspace.

github-actions · 2026-04-14T10:59:10Z

Successfully updated file versions.jsonfrom branch main into this PR in commit 7fa4034

github-actions · 2026-04-14T11:09:22Z

Publish workflow has completed with success.

Publishing process

✅ Finished successfully.

Published container images:
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-bulk-import:pr_2154__7.2.1
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-bulk-import-backend:pr_2154__7.2.1

Backstage-incompatible workspaces

Some workspaces have a backstage version (in sources or in their overlay folder) which is incompatible with the target Backstage version (1.49.4).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/bulk-import	1.47.3	⚪	BS Version History

How to fix

You have 3 main options:

Use the already-opened PR : For automatically-discovered workspaces, there might already be an automatically-opened PR that updates the commit to the target backstage version (Automatic PR link in column 4 above): just publish the plugins and test them from the PR by following the PR instructions.
Manually update the workspace commit :
- Find a newer commit, with a backstage version compatible with the target backstage version :__*
  - Backstage version history available: A BS Version History link might be available in column 4: in the workspace source repository, it points to the list of commits touching the backstage.json file. This would help you finding out whether this workspace has a commit that has been published for the target backstage version.
  - No info available: If no information is is provided in column 4, the backstage.json probably does not exist in workspace sources. You would have to look deeper into the newer commits of workspace sources, possibly in the low-level dependencies in the package.json files, to find out a commit with an underlying backstage version compatible with the target backstage version.
- Then, in the overlay repository, update the repo-ref field of the source.json file to the new source commit, and remember to also change the repo-backstage-version field to the corresponding compatible backstage version.
No compatible commit : If the workspace sources contain no compatible newer commit ( == a commit that provides a backstage.json version compatible with the target backstage), but the current workspace commit is known to work with the target backstage version, then you can override the declared backstage version compatibility for this workspace commit in the overlay repository: add a backstage.json file at the root of the overlay workspace folder with the desired target backstage version. This would require full testing of the workspace plugins on the target backstage though.

Metadata Validation

✅ All metadata files validated successfully.

No E2E tests available for this workspace.

PatAKnight · 2026-04-16T17:30:23Z

/update-commit

github-actions · 2026-04-16T17:36:19Z

Publish workflow has completed with failure.

github-actions · 2026-04-16T17:37:01Z

Update Commit workflow has completed with failure.

github-actions · 2026-04-16T17:41:29Z

Publish workflow has completed with success.

Publishing process

✅ Finished successfully.

Published container images:
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-bulk-import:pr_2154__7.2.1
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-bulk-import-backend:pr_2154__7.2.1

Backstage-incompatible workspaces

Some workspaces have a backstage version (in sources or in their overlay folder) which is incompatible with the target Backstage version (1.49.4).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/bulk-import	1.47.3	⚪	BS Version History

How to fix

You have 3 main options:

Use the already-opened PR : For automatically-discovered workspaces, there might already be an automatically-opened PR that updates the commit to the target backstage version (Automatic PR link in column 4 above): just publish the plugins and test them from the PR by following the PR instructions.
Manually update the workspace commit :
- Find a newer commit, with a backstage version compatible with the target backstage version :__*
  - Backstage version history available: A BS Version History link might be available in column 4: in the workspace source repository, it points to the list of commits touching the backstage.json file. This would help you finding out whether this workspace has a commit that has been published for the target backstage version.
  - No info available: If no information is is provided in column 4, the backstage.json probably does not exist in workspace sources. You would have to look deeper into the newer commits of workspace sources, possibly in the low-level dependencies in the package.json files, to find out a commit with an underlying backstage version compatible with the target backstage version.
- Then, in the overlay repository, update the repo-ref field of the source.json file to the new source commit, and remember to also change the repo-backstage-version field to the corresponding compatible backstage version.
No compatible commit : If the workspace sources contain no compatible newer commit ( == a commit that provides a backstage.json version compatible with the target backstage), but the current workspace commit is known to work with the target backstage version, then you can override the declared backstage version compatibility for this workspace commit in the overlay repository: add a backstage.json file at the root of the overlay workspace folder with the desired target backstage version. This would require full testing of the workspace plugins on the target backstage though.

Metadata Validation

✅ All metadata files validated successfully.

No E2E tests available for this workspace.

github-actions · 2026-04-16T17:46:48Z

Publish workflow has completed with success.

Publishing process

✅ Finished successfully.

Published container images:
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-bulk-import:pr_2154__7.2.1
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-bulk-import-backend:pr_2154__7.2.1

Backstage-incompatible workspaces

Some workspaces have a backstage version (in sources or in their overlay folder) which is incompatible with the target Backstage version (1.49.4).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/bulk-import	1.47.3	⚪	BS Version History

How to fix

You have 3 main options:

Use the already-opened PR : For automatically-discovered workspaces, there might already be an automatically-opened PR that updates the commit to the target backstage version (Automatic PR link in column 4 above): just publish the plugins and test them from the PR by following the PR instructions.
Manually update the workspace commit :
- Find a newer commit, with a backstage version compatible with the target backstage version :__*
  - Backstage version history available: A BS Version History link might be available in column 4: in the workspace source repository, it points to the list of commits touching the backstage.json file. This would help you finding out whether this workspace has a commit that has been published for the target backstage version.
  - No info available: If no information is is provided in column 4, the backstage.json probably does not exist in workspace sources. You would have to look deeper into the newer commits of workspace sources, possibly in the low-level dependencies in the package.json files, to find out a commit with an underlying backstage version compatible with the target backstage version.
- Then, in the overlay repository, update the repo-ref field of the source.json file to the new source commit, and remember to also change the repo-backstage-version field to the corresponding compatible backstage version.
No compatible commit : If the workspace sources contain no compatible newer commit ( == a commit that provides a backstage.json version compatible with the target backstage), but the current workspace commit is known to work with the target backstage version, then you can override the declared backstage version compatibility for this workspace commit in the overlay repository: add a backstage.json file at the root of the overlay workspace folder with the desired target backstage version. This would require full testing of the workspace plugins on the target backstage though.

Metadata Validation

✅ All metadata files validated successfully.

No E2E tests available for this workspace.

davidfestal · 2026-04-20T15:34:01Z

/update-commit

github-actions · 2026-04-20T15:40:52Z

Update Commit workflow has completed with failure.

github-actions · 2026-04-20T15:46:42Z

Publish workflow has completed with success.

Publishing process

✅ Finished successfully.

Published container images:
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-bulk-import:pr_2154__7.2.1
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-bulk-import-backend:pr_2154__7.2.1

Backstage-incompatible workspaces

Some workspaces have a backstage version (in sources or in their overlay folder) which is incompatible with the target Backstage version (1.49.4).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/bulk-import	1.47.3	⚪	BS Version History

How to fix

You have 3 main options:

Use the already-opened PR : For automatically-discovered workspaces, there might already be an automatically-opened PR that updates the commit to the target backstage version (Automatic PR link in column 4 above): just publish the plugins and test them from the PR by following the PR instructions.
Manually update the workspace commit :
- Find a newer commit, with a backstage version compatible with the target backstage version :__*
  - Backstage version history available: A BS Version History link might be available in column 4: in the workspace source repository, it points to the list of commits touching the backstage.json file. This would help you finding out whether this workspace has a commit that has been published for the target backstage version.
  - No info available: If no information is is provided in column 4, the backstage.json probably does not exist in workspace sources. You would have to look deeper into the newer commits of workspace sources, possibly in the low-level dependencies in the package.json files, to find out a commit with an underlying backstage version compatible with the target backstage version.
- Then, in the overlay repository, update the repo-ref field of the source.json file to the new source commit, and remember to also change the repo-backstage-version field to the corresponding compatible backstage version.
No compatible commit : If the workspace sources contain no compatible newer commit ( == a commit that provides a backstage.json version compatible with the target backstage), but the current workspace commit is known to work with the target backstage version, then you can override the declared backstage version compatibility for this workspace commit in the overlay repository: add a backstage.json file at the root of the overlay workspace folder with the desired target backstage version. This would require full testing of the workspace plugins on the target backstage though.

Metadata Validation

✅ All metadata files validated successfully.

No E2E tests available for this workspace.

davidfestal · 2026-04-20T16:20:31Z

/update-commit

github-actions · 2026-04-20T16:27:04Z

Update Commit workflow has completed with success.

github-actions · 2026-04-20T16:32:41Z

Publish workflow has completed with success.

Publishing process

✅ Finished successfully.

Published container images:
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-bulk-import:pr_2154__7.2.1
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-bulk-import-backend:pr_2154__7.2.1

Backstage-incompatible workspaces

Some workspaces have a backstage version (in sources or in their overlay folder) which is incompatible with the target Backstage version (1.49.4).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/bulk-import	1.47.3	⚪	BS Version History

How to fix

You have 3 main options:

Use the already-opened PR : For automatically-discovered workspaces, there might already be an automatically-opened PR that updates the commit to the target backstage version (Automatic PR link in column 4 above): just publish the plugins and test them from the PR by following the PR instructions.
Manually update the workspace commit :
- Find a newer commit, with a backstage version compatible with the target backstage version :__*
  - Backstage version history available: A BS Version History link might be available in column 4: in the workspace source repository, it points to the list of commits touching the backstage.json file. This would help you finding out whether this workspace has a commit that has been published for the target backstage version.
  - No info available: If no information is is provided in column 4, the backstage.json probably does not exist in workspace sources. You would have to look deeper into the newer commits of workspace sources, possibly in the low-level dependencies in the package.json files, to find out a commit with an underlying backstage version compatible with the target backstage version.
- Then, in the overlay repository, update the repo-ref field of the source.json file to the new source commit, and remember to also change the repo-backstage-version field to the corresponding compatible backstage version.
No compatible commit : If the workspace sources contain no compatible newer commit ( == a commit that provides a backstage.json version compatible with the target backstage), but the current workspace commit is known to work with the target backstage version, then you can override the declared backstage version compatibility for this workspace commit in the overlay repository: add a backstage.json file at the root of the overlay workspace folder with the desired target backstage version. This would require full testing of the workspace plugins on the target backstage though.

Metadata Validation

✅ All metadata files validated successfully.

No E2E tests available for this workspace.

christoph-jerolimov · 2026-04-22T16:06:25Z

/publish

christoph-jerolimov

/ok-to-test
/lgtm

github-actions · 2026-04-22T22:12:36Z

Publish workflow has completed with failure.

Backstage-incompatible workspaces

Some workspaces have a backstage version (in sources or in their overlay folder) which is incompatible with the target Backstage version (1.49.4).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/bulk-import	1.47.3	⚪	BS Version History

How to fix

You have 3 main options:

Use the already-opened PR : For automatically-discovered workspaces, there might already be an automatically-opened PR that updates the commit to the target backstage version (Automatic PR link in column 4 above): just publish the plugins and test them from the PR by following the PR instructions.
Manually update the workspace commit :
- Find a newer commit, with a backstage version compatible with the target backstage version :__*
  - Backstage version history available: A BS Version History link might be available in column 4: in the workspace source repository, it points to the list of commits touching the backstage.json file. This would help you finding out whether this workspace has a commit that has been published for the target backstage version.
  - No info available: If no information is is provided in column 4, the backstage.json probably does not exist in workspace sources. You would have to look deeper into the newer commits of workspace sources, possibly in the low-level dependencies in the package.json files, to find out a commit with an underlying backstage version compatible with the target backstage version.
- Then, in the overlay repository, update the repo-ref field of the source.json file to the new source commit, and remember to also change the repo-backstage-version field to the corresponding compatible backstage version.
No compatible commit : If the workspace sources contain no compatible newer commit ( == a commit that provides a backstage.json version compatible with the target backstage), but the current workspace commit is known to work with the target backstage version, then you can override the declared backstage version compatibility for this workspace commit in the overlay repository: add a backstage.json file at the root of the overlay workspace folder with the desired target backstage version. This would require full testing of the workspace plugins on the target backstage though.

davidfestal · 2026-04-23T12:26:47Z

@christoph-jerolimov The backstage version of the bulk-import workspace is still 1.47.3.

So either:

the source workspace should be upgraded to 1.49, and this PR be updated with /update-commit
or it should be guaranteed (== tested ?) that this workspace is still compatible with Backstage 1.49 and this should be explicitly stated by adding a backstage.json override with the 1.49.4 in the overlay workspace folder.

github-actions · 2026-04-23T13:34:10Z

Publish workflow has completed with success.

Publishing process

✅ Finished successfully.

Published container images:
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-bulk-import:pr_2154__7.2.1
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-bulk-import-backend:pr_2154__7.2.1

Backstage-incompatible workspaces

Some workspaces have a backstage version (in sources or in their overlay folder) which is incompatible with the target Backstage version (1.49.4).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/bulk-import	1.47.3	⚪	BS Version History

How to fix

You have 3 main options:

Use the already-opened PR : For automatically-discovered workspaces, there might already be an automatically-opened PR that updates the commit to the target backstage version (Automatic PR link in column 4 above): just publish the plugins and test them from the PR by following the PR instructions.
Manually update the workspace commit :
- Find a newer commit, with a backstage version compatible with the target backstage version :__*
  - Backstage version history available: A BS Version History link might be available in column 4: in the workspace source repository, it points to the list of commits touching the backstage.json file. This would help you finding out whether this workspace has a commit that has been published for the target backstage version.
  - No info available: If no information is is provided in column 4, the backstage.json probably does not exist in workspace sources. You would have to look deeper into the newer commits of workspace sources, possibly in the low-level dependencies in the package.json files, to find out a commit with an underlying backstage version compatible with the target backstage version.
- Then, in the overlay repository, update the repo-ref field of the source.json file to the new source commit, and remember to also change the repo-backstage-version field to the corresponding compatible backstage version.
No compatible commit : If the workspace sources contain no compatible newer commit ( == a commit that provides a backstage.json version compatible with the target backstage), but the current workspace commit is known to work with the target backstage version, then you can override the declared backstage version compatibility for this workspace commit in the overlay repository: add a backstage.json file at the root of the overlay workspace folder with the desired target backstage version. This would require full testing of the workspace plugins on the target backstage though.

Metadata Validation

✅ All metadata files validated successfully.

No E2E tests available for this workspace.

christoph-jerolimov · 2026-04-26T05:57:01Z

/update-commit

github-actions · 2026-04-26T06:02:46Z

Update Commit workflow has completed with success.

github-actions · 2026-04-26T06:07:57Z

Publish workflow has completed with success.

Publishing process

✅ Finished successfully.

Published container images:
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-bulk-import:pr_2154__7.2.1
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-bulk-import-backend:pr_2154__7.2.1

Backstage-incompatible workspaces

Some workspaces have a backstage version (in sources or in their overlay folder) which is incompatible with the target Backstage version (1.49.4).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/bulk-import	1.47.3	⚪	BS Version History

How to fix

You have 3 main options:

Use the already-opened PR : For automatically-discovered workspaces, there might already be an automatically-opened PR that updates the commit to the target backstage version (Automatic PR link in column 4 above): just publish the plugins and test them from the PR by following the PR instructions.
Manually update the workspace commit :
- Find a newer commit, with a backstage version compatible with the target backstage version :__*
  - Backstage version history available: A BS Version History link might be available in column 4: in the workspace source repository, it points to the list of commits touching the backstage.json file. This would help you finding out whether this workspace has a commit that has been published for the target backstage version.
  - No info available: If no information is is provided in column 4, the backstage.json probably does not exist in workspace sources. You would have to look deeper into the newer commits of workspace sources, possibly in the low-level dependencies in the package.json files, to find out a commit with an underlying backstage version compatible with the target backstage version.
- Then, in the overlay repository, update the repo-ref field of the source.json file to the new source commit, and remember to also change the repo-backstage-version field to the corresponding compatible backstage version.
No compatible commit : If the workspace sources contain no compatible newer commit ( == a commit that provides a backstage.json version compatible with the target backstage), but the current workspace commit is known to work with the target backstage version, then you can override the declared backstage version compatibility for this workspace commit in the overlay repository: add a backstage.json file at the root of the overlay workspace folder with the desired target backstage version. This would require full testing of the workspace plugins on the target backstage though.

Metadata Validation

✅ All metadata files validated successfully.

No E2E tests available for this workspace.

davidfestal · 2026-04-27T13:08:10Z

/update-commit

…9.3` on branch `main`

openshift-ci · 2026-04-27T13:14:22Z

New changes are detected. LGTM label has been removed.

github-actions · 2026-04-27T13:14:48Z

Update Commit workflow has completed with success.

sonarqubecloud · 2026-04-27T13:14:57Z

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

github-actions · 2026-04-27T13:20:21Z

Publish workflow has completed with success.

Publishing process

✅ Finished successfully.

Published container images:
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-bulk-import:pr_2154__7.3.0
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-bulk-import-backend:pr_2154__7.3.0

Backstage Compatibility Check

✅ All workspaces are compatible with the target Backstage version (1.49.4).

No action required.

Metadata Validation

✅ All metadata files validated successfully.

No E2E tests available for this workspace.

github-actions · 2026-04-27T13:23:57Z

✅ Smoke tests workflow passed. All plugins loaded successfully.

github-actions · 2026-04-27T13:37:23Z

Publish workflow has completed with success.

Publishing process

✅ Finished successfully.

Published container images:
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-bulk-import:pr_2154__7.3.0
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-bulk-import-backend:pr_2154__7.3.0

Backstage Compatibility Check

✅ All workspaces are compatible with the target Backstage version (1.49.4).

No action required.

Metadata Validation

✅ All metadata files validated successfully.

No E2E tests available for this workspace.

github-actions · 2026-04-27T13:41:11Z

✅ Smoke tests workflow passed. All plugins loaded successfully.

Update bulk-import workspace to commit 476c4e8 for backstage `1.4…

6998fb6

…7.3` on branch `main`

github-actions Bot requested review from a team, debsmita1, its-mitesh-kumar and rm3l as code owners April 4, 2026 15:16

openshift-ci Bot added the needs-ok-to-test label Apr 4, 2026

github-actions Bot added mandatory-workspace PR affects a workspace with required plugins for releases workspace-update PR modifies files in an existing workspace labels Apr 4, 2026

chore: sync versions.json from main

a8c4194

github-actions Bot requested review from a team, gashcrumb and kadel as code owners April 8, 2026 18:04

chore: sync versions.json from main

b7e8408

chore: sync versions.json from main

7fa4034

christoph-jerolimov approved these changes Apr 22, 2026

View reviewed changes

openshift-ci Bot added ok-to-test and removed needs-ok-to-test labels Apr 22, 2026

openshift-ci Bot assigned christoph-jerolimov Apr 22, 2026

openshift-ci Bot added the lgtm label Apr 22, 2026

Update bulk-import workspace to commit dbc4e81 for backstage `1.4…

f928e6c

…9.3` on branch `main`

github-actions Bot changed the title ~~Update bulk-import workspace to commit 476c4e8 for backstage 1.47.3 on branch main~~ Update bulk-import workspace to commit dbc4e81 for backstage 1.49.3 on branch main Apr 27, 2026

openshift-ci Bot removed the lgtm label Apr 27, 2026

davidfestal merged commit 60ff51f into main Apr 27, 2026
5 checks passed

davidfestal deleted the workspaces/main__bulk-import branch April 27, 2026 13:42

Conversation

github-actions Bot commented Apr 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci Bot commented Apr 4, 2026

Uh oh!

github-actions Bot commented Apr 4, 2026

Publishing process

Backstage-incompatible workspaces

Metadata Validation

Uh oh!

github-actions Bot commented Apr 8, 2026

Uh oh!

github-actions Bot commented Apr 9, 2026

Publishing process

Backstage-incompatible workspaces

Metadata Validation

Uh oh!

github-actions Bot commented Apr 9, 2026

Uh oh!

github-actions Bot commented Apr 9, 2026

Publishing process

Backstage-incompatible workspaces

Metadata Validation

Uh oh!

github-actions Bot commented Apr 14, 2026

Uh oh!

github-actions Bot commented Apr 14, 2026

Publishing process

Backstage-incompatible workspaces

Metadata Validation

Uh oh!

PatAKnight commented Apr 16, 2026

Uh oh!

github-actions Bot commented Apr 16, 2026

Uh oh!

github-actions Bot commented Apr 16, 2026

Uh oh!

github-actions Bot commented Apr 16, 2026

Publishing process

Backstage-incompatible workspaces

Metadata Validation

Uh oh!

github-actions Bot commented Apr 16, 2026

Publishing process

Backstage-incompatible workspaces

Metadata Validation

Uh oh!

davidfestal commented Apr 20, 2026

Uh oh!

github-actions Bot commented Apr 20, 2026

Uh oh!

github-actions Bot commented Apr 20, 2026

Publishing process

Backstage-incompatible workspaces

Metadata Validation

Uh oh!

davidfestal commented Apr 20, 2026

Uh oh!

github-actions Bot commented Apr 20, 2026

Uh oh!

github-actions Bot commented Apr 20, 2026

Publishing process

Backstage-incompatible workspaces

Metadata Validation

Uh oh!

christoph-jerolimov commented Apr 22, 2026

Uh oh!

christoph-jerolimov left a comment

Choose a reason for hiding this comment

Uh oh!

github-actions Bot commented Apr 22, 2026

Backstage-incompatible workspaces

Uh oh!

davidfestal commented Apr 23, 2026

Uh oh!

github-actions Bot commented Apr 23, 2026

Publishing process

Backstage-incompatible workspaces

Metadata Validation

github-actions Bot commented Apr 4, 2026 •

edited

Loading