Update acr workspace to commit 0b1778e for backstage 1.49.2 on branch main#2253
Update acr workspace to commit 0b1778e for backstage 1.49.2 on branch main#2253github-actions[bot] wants to merge 1 commit intomainfrom
acr workspace to commit 0b1778e for backstage 1.49.2 on branch main#2253Conversation
|
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 Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
|
|
Publish workflow has completed with success. Publishing process✅ Finished successfully.
Backstage Compatibility Check✅ All workspaces are compatible with the target Backstage version ( No action required. Metadata Validation✅ All metadata files validated successfully. Running e2e tests |
|
@github-actions[bot]: Cannot trigger testing until a trusted user reviews the PR and leaves an DetailsIn response to this:
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. |
|
✅ Smoke tests workflow passed. All plugins loaded successfully. |



Update acr workspace at commit backstage/community-plugins@0b1778e for backstage
1.49.2on branchmain.This PR was created automatically.
Click on the following link to see the source diff it introduces: backstage/community-plugins@8cff941...0b1778e.
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: