Manually add pagerduty workspace to commit d8dc915 for backstage 1.40.0 on branch main
#1556
Conversation
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
|
/publish |
|
Publish workflow has completed with failure. |
…`1.40.0` on branch `main` Signed-off-by: David Festal <[email protected]>
davidfestal
force-pushed
the
workspaces/main__pagerduty
branch
from
391756d to
dde137f
Compare
|
/publish |
|
Publish workflow has completed with failure. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Manually add pagerduty workspace at commit PagerDuty/backstage-plugins@d8dc915 for backstage
1.40.0on branchmain.This PR was created manually.
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.jsonfile 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-versionfield insource.jsonaccordingly.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.jsonfile 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-versionfield insource.jsonaccordingly.You might need to complete it with additional dynamic plugin export information, like:
app-config.dynamic.yamlfile for frontend plugins,scalprum-config.jsonfile 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
/publishinstruction in a PR review comment.This will start a PR check workflow to: