Skip to content

Update rbac workspace to commit 456e426 for backstage 1.52.0 on branch main - #3198

Open
github-actions[bot] wants to merge 2 commits into
mainfrom
workspaces/main__rbac
Open

Update rbac workspace to commit 456e426 for backstage 1.52.0 on branch main#3198
github-actions[bot] wants to merge 2 commits into
mainfrom
workspaces/main__rbac

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Update rbac workspace at commit backstage/community-plugins@456e426 for backstage 1.52.0 on branch main.

This PR was created automatically.
Click on the following link to see the source diff it introduces: backstage/community-plugins@2e59d04...456e426.

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

openshift-ci Bot commented Aug 7, 2026

Copy link
Copy Markdown

PR needs rebase.

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.

@openshift-ci

openshift-ci Bot commented Aug 7, 2026

Copy link
Copy Markdown

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.

@sonarqubecloud

sonarqubecloud Bot commented Aug 7, 2026

Copy link
Copy Markdown

@github-actions 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 Aug 7, 2026
@github-actions

github-actions Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor Author

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

github-actions Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor Author

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

@github-actions

Copy link
Copy Markdown
Contributor Author

A new workspace commit 949d6784a47012fd40af061956189c9ff244891c 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

Copy link
Copy Markdown
Contributor Author

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

Copy link
Copy Markdown
Contributor Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

mandatory-workspace PR affects a workspace with required plugins for releases needs-commit-update needs-ok-to-test needs-rebase workspace-update PR modifies files in an existing workspace

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants