Update scaffolder-relation-processor workspace to commit 65b7440 for backstage 1.45.3 on branch main#97
Open
github-actions[bot] wants to merge 2 commits into
Conversation
Signed-off-by: rostalan <rlan@redhat.com>
…for backstage `1.45.3` on branch `main`
github-actions
Bot
added
mandatory-workspace
Author
|
This pull request has been automatically marked as stale due to inactivity. |
rostalan
force-pushed
the
main
branch
6 times, most recently
from
a94232a to
77f7391
Compare
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
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.
Update scaffolder-relation-processor workspace at commit backstage/community-plugins@65b7440 for backstage
1.45.3on branchmain.This PR was created automatically.
Click on the following link to see the source diff it introduces: backstage/community-plugins@bcc499d...65b7440.
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: