Update konflux workspace to commit 815320b for backstage 1.52.0 on branch main

[rrosatti]

Description

I resolved the conflicts on #2839 , but I don't have permissions to push the changes. So, I created a new up-to-date PR. The text bellow is a copy/paste from #2839 description ->

---

Update konflux workspace at commit redhat-developer/rhdh-plugins@815320b for backstage 1.49.4 on branch main.

This PR was created automatically.

⚠️ Manual approval required
This proposal is a Best-Effort Backstage compatibility match. Plugin sources are built for Backstage 1.49.4. Please review and test before merging.

If you have tested and confirmed compatibility, you should add a backstage.json file in the workspace folder to override the known Backstage compatibility to be the target Backstage version.

Click on the following link to see the source diff it introduces: redhat-developer/rhdh-plugins@d2b42a2...815320b.

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.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[rrosatti]

/test all

[openshift-ci]

@rrosatti: No jobs can be run with /test all.
The following commands are available to trigger optional jobs:

/test e2e-ocp-helm

/test e2e-ocp-helm-nightly

Details

In response to this:

/test all

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.

[rrosatti]

/publish

[github-actions]

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-konflux:pr_3266__0.2.0
• ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-konflux-backend:pr_3266__0.2.0

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.52.0).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/konflux	1.49.4	⚪	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 using the /override-backstage command which will 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.

[rrosatti]

/override-backstage

[github-actions]

Override Backstage workflow — skipped: PR is from a fork.

Please manually:

1. Create backstage.json with {"version": "1.52.0"}
2. Update all metadata/*.yaml OCI tags from bs_<old>__ to bs_1.52.0__
3. Update supportedVersions in all metadata/*.yaml to 1.52.0

[rrosatti]

/publish

[sonarqubecloud]

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]

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-konflux:pr_3266__0.2.0
• ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-konflux-backend:pr_3266__0.2.0

Backstage Compatibility Check

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

No action required.

Metadata Validation

✅ All metadata files validated successfully.

No E2E tests available for this workspace.

[github-actions]

✅ Smoke tests workflow passed. All plugins loaded successfully.

[rrosatti]

tested the published oci image with a local running rhdh instance and it seems to be alright:

rhdh-local-test-pr_3266__0.2.0-image.mov