Update `app-defaults` workspace to commit `a04cf01` for backstage `1.52.1` on branch `main` by github-actions[bot] · Pull Request #2783 · redhat-developer/rhdh-plugin-export-overlays

github-actions · 2026-07-15T13:08:06Z

Update app-defaults workspace at commit redhat-developer/rhdh-plugins@a04cf01 for backstage 1.52.1 on branch main.

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

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.

…49.3` on branch `main`

openshift-ci · 2026-07-15T13:08:19Z

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-07-15T13:37:18Z

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-app-auth:pr_2783__0.0.3
ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-app-integrations:pr_2783__0.0.2

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/app-defaults	1.49.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 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.

Running e2e tests
/test e2e-ocp-helm

openshift-ci · 2026-07-15T13:37:38Z

@github-actions[bot]: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

Details

In response to this:

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-app-auth:pr_2783__0.0.3

ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-app-integrations:pr_2783__0.0.2

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/app-defaults 1.49.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 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.

Running e2e tests
/test e2e-ocp-helm

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.

gashcrumb · 2026-07-15T13:52:45Z

/ok-to-test

gashcrumb · 2026-07-15T13:54:01Z

/update-commit

github-actions · 2026-07-15T13:55:36Z

Update Commit workflow has completed with success.

github-actions · 2026-07-15T14:00: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-app-auth:pr_2783__0.0.3
ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-app-integrations:pr_2783__0.0.2

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/app-defaults	1.49.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 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.

Running e2e tests
/test e2e-ocp-helm

rhdh-test-bot · 2026-07-15T14:13:58Z

❌ Failed E2E Tests - `app-defaults`

gashcrumb · 2026-07-15T14:24:29Z

hmm, guess I shouldn't have moved these to 1.52.1, the workflow is only going to pick the older 1.49.3 version as it's not above what RHDH is currently pointing to.

gashcrumb · 2026-07-15T16:08:47Z

let's wait for redhat-developer/rhdh-plugin-export-utils#151 and then this should pick up the right version of the plugin.

…49.3` on branch `main`

github-actions · 2026-07-23T20:01:52Z

A new workspace commit a04cf01e4ba573ec9b8b6912afe3812fa280d61c has been discovered (match type: 'exact').
You can update this PR with the latest discovered workspace source commit.

To do so, you can use the /update-commit instruction in a PR review comment.

github-actions · 2026-07-23T20:27:52Z

The versions.json file in your PR doesn't match the one in release branch main
Try updating it by adding the /update-versions PR comment.

github-actions · 2026-07-23T20:28:14Z

Publish workflow — blocked: versions.json is not up-to-date with the base branch.

gashcrumb · 2026-07-24T11:17:23Z

/update-versions

github-actions · 2026-07-24T11:17:58Z

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

github-actions · 2026-07-24T11:18:18Z

Update Versions workflow has completed with success.

gashcrumb · 2026-07-24T11:19:25Z

/update-commit

…52.1` on branch `main`

github-actions · 2026-07-24T11:20:52Z

Update Commit workflow has completed with success.

github-actions · 2026-07-24T11:22: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-app-auth:pr_2783__0.0.3
ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-app-integrations:pr_2783__0.0.2

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/app-defaults	1.49.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 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.

Running e2e tests
/test e2e-ocp-helm

github-actions · 2026-07-24T11:28:12Z

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-app-auth:pr_2783__0.1.0
ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-app-integrations:pr_2783__0.1.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.

Running e2e tests
/test e2e-ocp-helm

github-actions · 2026-07-24T11:31:34Z

✅ Smoke tests workflow passed. All plugins loaded successfully.

Resolve app-defaults metadata conflicts by keeping the 0.1.0 / bs_1.52.0 package versions from this PR while dropping the legacy !package OCI suffix to match main. Co-authored-by: Cursor <cursoragent@cursor.com> rh-pre-commit.version: 2.3.2 rh-pre-commit.check-secrets: ENABLED

sonarqubecloud · 2026-07-24T12:19:20Z

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

gashcrumb · 2026-07-24T12:19:33Z

/publish

github-actions · 2026-07-24T12:24:45Z

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-app-auth:pr_2783__0.1.0
ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-app-integrations:pr_2783__0.1.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.

Running e2e tests
/test e2e-ocp-helm

github-actions · 2026-07-24T12:29:33Z

✅ Smoke tests workflow passed. All plugins loaded successfully.

rhdh-test-bot · 2026-07-24T12:42:53Z

✅ Passed E2E Tests - `app-defaults`

fullsend-ai-retro · 2026-07-24T13:09:15Z

🤖 Finished Retro · ✅ Success · Started 1:09 PM UTC · Completed 1:20 PM UTC
Commit: 886295b · View workflow run →

fullsend-ai-retro · 2026-07-24T13:20:44Z

Retro: PR #2783 — `app-defaults` workspace update

PR type: Automated workspace-update (bot-generated by update-plugins-repo-refs.yaml)
Lifecycle: 9 days (Jul 15 → Jul 24) — slow tier for workspace-update PRs (median is ~3.6 days)
Agent involvement: None. The fullsend workflow was installed in this repo on Jul 22, after PR creation (Jul 15). The router correctly dispatched only the retro agent on merge.

What happened

Jul 15: Automation created PR to update app-defaults workspace to Backstage 1.49.3. The publish workflow detected Backstage version incompatibility (1.49.3 vs target 1.52.0) and flagged it as "non-mandatory," but still auto-triggered /test e2e-ocp-helm.
Jul 15: E2E tests failed 0/3 — the incompatible Backstage version caused deployment failures. Maintainer (gashcrumb) diagnosed the issue and identified an upstream dependency (rhdh-plugin-export-utils PR #151) that needed to land first.
Jul 15–23: PR sat dormant waiting for the upstream fix.
Jul 23: Daily discovery workflow found new commit a04cf01 at Backstage 1.52.1.
Jul 24: Maintainer ran /update-versions (to fix versions.json drift), /update-commit, and /publish. All checks passed — Backstage compatibility, smoke tests, E2E tests (3/3). PR merged.

Key observations

25% of workspace-update PRs (8 of 32 sampled) hit the same Backstage version incompatibility pattern. This is structural, not a one-off.
The wasted E2E run on Jul 15 consumed ~5 min of cluster compute on a doomed test. The publish workflow already knew the versions were incompatible but auto-triggered E2E anyway.
The fullsend router worked correctly — it skipped review/code agents for bot-generated PR events and only dispatched retro on merge. No agent-side improvements are needed.
4 currently-open workspace-update PRs (Update konflux workspace to commit 815320b for backstage 1.49.4 on branch main #2839, Add icon-viewer workspace to commit a0cb7b9 for backstage 1.48.3 on branch main #2836, Add gitlab workspace to commit 7c92d27 for backstage 1.48.3 on branch main #2835, Add github-notifications workspace to commit 4f2fc8b for backstage 1.48.5 on branch main #2834) show the same incompatibility pattern right now, suggesting the structural issue persists.

Evidence supporting existing issues

#2870 (auto-apply backstage compatibility override): PR Update app-defaults workspace to commit a04cf01 for backstage 1.52.1 on branch main #2783 is another instance of the same pattern — a best-effort Backstage match caused a wasted E2E run and an 8-day delay. If the override had been auto-applied at PR creation, the first E2E run on Jul 15 could have succeeded.
#2879 (don't auto-trigger E2E without /ok-to-test): The publish workflow on Jul 15 auto-triggered /test e2e-ocp-helm despite detecting incompatibility. This wasted CI resources on a test that was guaranteed to fail.
#2816 (auto-sync versions.json): On Jul 24, the first publish attempt was blocked because versions.json was out of sync with the base branch. The maintainer had to manually run /update-versions before publishing could proceed.

No new proposals

All improvement opportunities identified in this retro are already covered by existing open issues (#2870, #2879, #2816). The fullsend agent infrastructure is newly installed and working as intended — no agent-layer changes are needed.

github-actions Bot added 3 commits June 11, 2026 13:58

Update app-defaults workspace to commit 3c91057 for backstage `1.…

5ea22f4

…49.3` on branch `main`

chore: sync versions.json from main

b9bfa8d

Update app-defaults workspace to commit 3c91057 for backstage `1.…

b266c57

…49.3` on branch `main`

github-actions Bot requested review from a team, gashcrumb and kadel as code owners July 15, 2026 13:08

openshift-ci Bot added the needs-ok-to-test label Jul 15, 2026

github-actions Bot added the workspace-update PR modifies files in an existing workspace label Jul 15, 2026

Merge branch 'main' into workspaces/main__app-defaults

2d8e125

openshift-ci Bot added ok-to-test and removed needs-ok-to-test labels Jul 15, 2026

Update app-defaults workspace to commit 3c91057 for backstage `1.…

b4fdf6f

…49.3` on branch `main`

openshift-ci Bot added the needs-rebase label Jul 22, 2026

github-actions Bot added the needs-commit-update label Jul 23, 2026

chore: sync versions.json from main

cb08277

Update app-defaults workspace to commit a04cf01 for backstage `1.…

61a3c28

…52.1` on branch `main`

github-actions Bot changed the title ~~Update app-defaults workspace to commit 3c91057 for backstage 1.49.3 on branch main~~ Update app-defaults workspace to commit a04cf01 for backstage 1.52.1 on branch main Jul 24, 2026

github-actions Bot removed the needs-commit-update label Jul 24, 2026

openshift-ci Bot removed the needs-rebase label Jul 24, 2026

gashcrumb merged commit 886295b into main Jul 24, 2026
14 checks passed

gashcrumb deleted the workspaces/main__app-defaults branch July 24, 2026 13:08

Uh oh!

Conversation

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

Uh oh!

Uh oh!

openshift-ci Bot commented Jul 15, 2026

Uh oh!

github-actions Bot commented Jul 15, 2026

Publishing process

Backstage-incompatible workspaces

Metadata Validation

Uh oh!

openshift-ci Bot commented Jul 15, 2026

Publishing process

Backstage-incompatible workspaces

Metadata Validation

Uh oh!

gashcrumb commented Jul 15, 2026

Uh oh!

gashcrumb commented Jul 15, 2026

Uh oh!

github-actions Bot commented Jul 15, 2026

Uh oh!

github-actions Bot commented Jul 15, 2026

Publishing process

Backstage-incompatible workspaces

Metadata Validation

Uh oh!

rhdh-test-bot commented Jul 15, 2026

❌ Failed E2E Tests - app-defaults

Uh oh!

gashcrumb commented Jul 15, 2026

Uh oh!

gashcrumb commented Jul 15, 2026

Uh oh!

github-actions Bot commented Jul 23, 2026

Uh oh!

github-actions Bot commented Jul 23, 2026

Uh oh!

github-actions Bot commented Jul 23, 2026

Uh oh!

gashcrumb commented Jul 24, 2026

Uh oh!

github-actions Bot commented Jul 24, 2026

Uh oh!

github-actions Bot commented Jul 24, 2026

Uh oh!

gashcrumb commented Jul 24, 2026

Uh oh!

github-actions Bot commented Jul 24, 2026

Uh oh!

github-actions Bot commented Jul 24, 2026

Publishing process

Backstage-incompatible workspaces

Metadata Validation

Uh oh!

github-actions Bot commented Jul 24, 2026

Publishing process

Backstage Compatibility Check

Metadata Validation

Uh oh!

github-actions Bot commented Jul 24, 2026

Uh oh!

sonarqubecloud Bot commented Jul 24, 2026

Quality Gate passed

Uh oh!

gashcrumb commented Jul 24, 2026

Uh oh!

github-actions Bot commented Jul 24, 2026

Publishing process

Backstage Compatibility Check

Metadata Validation

Uh oh!

github-actions Bot commented Jul 24, 2026

Uh oh!

rhdh-test-bot commented Jul 24, 2026

✅ Passed E2E Tests - app-defaults

Uh oh!

Uh oh!

fullsend-ai-retro Bot commented Jul 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

github-actions Bot commented Jul 15, 2026 •

edited

Loading

❌ Failed E2E Tests - `app-defaults`

✅ Passed E2E Tests - `app-defaults`

fullsend-ai-retro Bot commented Jul 24, 2026 •

edited

Loading

Retro: PR #2783 — `app-defaults` workspace update