Update backstage workspace to commit v1.49.4 for backstage 1.49.4 on branch main#104
Open
github-actions[bot] wants to merge 1 commit into
Open
Update backstage workspace to commit v1.49.4 for backstage 1.49.4 on branch main#104github-actions[bot] wants to merge 1 commit into
backstage workspace to commit v1.49.4 for backstage 1.49.4 on branch main#104github-actions[bot] wants to merge 1 commit into
Conversation
…4` on branch `main`
github-actions
Bot
added
mandatory-workspace
Author
|
Publish workflow has completed with failure. Backstage Compatibility Check✅ All workspaces are compatible with the target Backstage version ( No action required. |
rostalan
force-pushed
the
main
branch
6 times, most recently
from
a94232a to
77f7391
Compare
rostalan
pushed a commit
that referenced
this pull request
May 27, 2026
…r ghcr.io plugins (redhat-developer#2480) * chore(e2e): bump e2e-test-utils to 1.1.43 across all workspaces Assisted-by: Claude Code Co-Authored-By: Claude Code <noreply@anthropic.com> * chore(e2e): set NIGHTLY_DPDY_OCI_REGISTRY_MAP for ghcr.io plugins in nightly mode Plugins whose artifacts live in ghcr.io (quay, tekton, homepage-backend) get {{inherit}} resolved against the wrong (RHEC) registry in nightly mode since e2e-test-utils PR #104. Set NIGHTLY_DPDY_OCI_REGISTRY_MAP in each affected spec's beforeAll to route them to the correct ghcr.io registry. Assisted-by: Claude Code Co-Authored-By: Claude Code <noreply@anthropic.com> * chore(e2e): improve NIGHTLY_DPDY_OCI_REGISTRY_MAP comments in spec files Assisted-by: Claude Code Co-Authored-By: Claude Code <noreply@anthropic.com> * chore(e2e): skip homepage nightly tests until RHDHBUGS-3190 is resolved homepage-backend is absent from the DPDY in the catalog index image despite being added to default.packages.yaml (rhdh PR #4828), causing {{inherit}} resolution to fail in nightly mode. Assisted-by: Claude Code Co-Authored-By: Claude Code <noreply@anthropic.com> * chore(e2e): remove NIGHTLY_DPDY_OCI_REGISTRY_MAP from homepage spec Superseded by the nightly skip added for RHDHBUGS-3190 — the override never runs since the suite skips in nightly mode. Assisted-by: Claude Code Co-Authored-By: Claude Code <noreply@anthropic.com> --------- Co-authored-by: Claude Code <noreply@anthropic.com>
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
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.
Update backstage workspace at commit backstage/backstage@v1.49.4 for backstage
1.49.4on branchmain.This PR was created automatically.
🎉 Override Can Be Removed!
The overlay currently contained an override at
workspaces/backstage/backstage.json. This upgrade is an Exact Match for Backstage1.49.4,, so the override has been removed.Click on the following link to see the source diff it introduces: backstage/backstage@v1.48.3...v1.49.4.
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
/publishinstruction in a PR review comment.This will start a PR check workflow to: