-
Notifications
You must be signed in to change notification settings - Fork 24
Add feedback
workspace to commit 5a061bb
for backstage 1.41.1
on branch main
#1464
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
…n branch `main`
/publish |
Publish workflow has completed with failure.
|
A new workspace commit 5a061bbdcaef888fed856654bb6fd6d92ebda3dc has been discovered (match type: 'best-effort'). To do so, you can use the |
Successfully updated file |
/update-commit |
…n branch `main`
feedback
workspace to commit 7027767
for backstage 1.41.1
on branch main
feedback
workspace to commit 5a061bb
for backstage 1.41.1
on branch main
Recommended actions after the commit update:
|
Update Commit workflow has completed with success. |
Add feedback workspace at commit backstage/community-plugins@5a061bb for backstage
1.41.1
on branchmain
.This PR was created automatically.
This proposal is a Best-Effort Backstage compatibility match. Plugin sources are built for Backstage
1.41.1
. 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.Don't forget to also update the
repo-backstage-version
field insource.json
accordingly.This proposal is a Best-Effort Backstage compatibility match. Plugin sources are built for Backstage
1.41.1
. 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.Don't forget to also update the
repo-backstage-version
field insource.json
accordingly.You might need to complete it with additional dynamic plugin export information, like:
app-config.dynamic.yaml
file for frontend plugins,scalprum-config.json
file for frontend plugins,patches/
directoryBefore 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: