Add matomo
workspace to commit e35fb62
for backstage 1.41.1
on branch main
#1467
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.
Add matomo workspace at commit backstage/community-plugins@e35fb62 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.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,patch
file at the workspace levelBefore 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: