Add matomo workspace to commit 3e2c0cf for backstage 1.41.1 on branch main

[github-actions]

Add matomo workspace at commit backstage/community-plugins@3e2c0cf for backstage 1.41.1 on branch main.

This PR was created automatically.

⚠️ Manual approval required
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 in source.json accordingly.

⚠️ Manual approval required
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 in source.json accordingly.

You might need to complete it with additional dynamic plugin export information, like:

• the associated app-config.dynamic.yaml file for frontend plugins,
• optionally the scalprum-config.json file for frontend plugins,
• optionally some overlay source files at the plugin level,
• optionally patches at the workspace level in the patches/ directory

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.

[github-actions]

Successfully updated file versions.jsonfrom branch main into this PR in commit d6c37e4

[github-actions]

A new workspace commit 3e2c0cf90b1b6a9c2fae063b5835a632fcf884d5 has been discovered (match type: 'best-effort').
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.

[davidfestal]

/update-commit

[github-actions]

Recommended actions after the commit update:

• Best-Effort upgrade with unknown backstage compatibility: After testing the plugins against the target backstage version, 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 in source.json accordingly.

[github-actions]

Update Commit workflow has completed with success.

[davidfestal]

/publish

[github-actions]

Publish workflow has completed with failure.

• Published container images:
  • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-matomo:pr_1467__1.13.1
  • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-matomo-backend:pr_1467__1.14.0

[davidfestal]

/publish

[github-actions]

Publish workflow has completed with failure.

Backstage-incompatible workspaces

Some workspaces have a backstage version (in sources or in their overlay folder) which is incompatible with the target Backstage version (1.42.5).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/matomo	1.41.1	⚪	BS Version History

How to fix

You have 3 main options:

• Use the already-opened PR : For automatically-discovered workspaces, there might already be an automatically-opened PR that updates the commit to the target backstage version (Automatic PR link in column 4 above): just publish the plugins and test them from the PR by following the PR instructions.

• Manually update the workspace commit :

  • Find a newer commit, with a backstage version compatible with the target backstage version :__*
    • Backstage version history available: A BS Version History link might be available in column 4: in the workspace source repository, it points to the list of commits touching the backstage.json file. This would help you finding out whether this workspace has a commit that has been published for the target backstage version.
    • No info available: If no information is is provided in column 4, the backstage.json probably does not exist in workspace sources. You would have to look deeper into the newer commits of workspace sources, possibly in the low-level dependencies in the package.json files, to find out a commit with an underlying backstage version compatible with the target backstage version.
  • Then, in the overlay repository, update the repo-ref field of the source.json file to the new source commit, and remember to also change the repo-backstage-version field to the corresponding compatible backstage version.

• No compatible commit : If the workspace sources contain no compatible newer commit ( == a commit that provides a backstage.json version compatible with the target backstage), but the current workspace commit is known to work with the target backstage version, then you can override the declared backstage version compatibility for this workspace commit in the overlay repository: add a backstage.json file at the root of the overlay workspace folder with the desired target backstage version, and remember to also change the repo-backstage-version field of the source.json file to the same target backstage version. This would require full testing of the workspace plugins on the target backstage though.

• Published container images:

  • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-matomo:pr_1467__1.13.1
  • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-matomo-backend:pr_1467__1.14.0

[davidfestal]

/update-commit

[github-actions]

Update Commit workflow has completed with success.

[github-actions]

This pull request has been automatically marked as stale due to inactivity.

[github-actions]

Successfully updated file versions.jsonfrom branch main into this PR in commit c343e86

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

Successfully updated file versions.jsonfrom branch main into this PR in commit b0ddc92

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

Successfully updated file versions.jsonfrom branch main into this PR in commit faa439d

[github-actions]

Publish workflow has completed with success.

Publishing process

✅ Finished successfully.

• Published container images:
  • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-matomo:pr_1467__1.13.1
  • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-matomo-backend:pr_1467__1.14.0

Backstage-incompatible workspaces

Some workspaces have a backstage version (in sources or in their overlay folder) which is incompatible with the target Backstage version (1.48.3).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/ocm	1.45.3	⚪	BS Version History

How to fix

You have 3 main options:

• Use the already-opened PR : For automatically-discovered workspaces, there might already be an automatically-opened PR that updates the commit to the target backstage version (Automatic PR link in column 4 above): just publish the plugins and test them from the PR by following the PR instructions.
• Manually update the workspace commit :
  • Find a newer commit, with a backstage version compatible with the target backstage version :__*
    • Backstage version history available: A BS Version History link might be available in column 4: in the workspace source repository, it points to the list of commits touching the backstage.json file. This would help you finding out whether this workspace has a commit that has been published for the target backstage version.
    • No info available: If no information is is provided in column 4, the backstage.json probably does not exist in workspace sources. You would have to look deeper into the newer commits of workspace sources, possibly in the low-level dependencies in the package.json files, to find out a commit with an underlying backstage version compatible with the target backstage version.
  • Then, in the overlay repository, update the repo-ref field of the source.json file to the new source commit, and remember to also change the repo-backstage-version field to the corresponding compatible backstage version.
• No compatible commit : If the workspace sources contain no compatible newer commit ( == a commit that provides a backstage.json version compatible with the target backstage), but the current workspace commit is known to work with the target backstage version, then you can override the declared backstage version compatibility for this workspace commit in the overlay repository: add a backstage.json file at the root of the overlay workspace folder with the desired target backstage version. This would require full testing of the workspace plugins on the target backstage though.

Metadata Validation

❌ Found 1 validation error(s):

File	Kind	Message
metadata	missing-file	Metadata directory not found at /home/runner/work/rhdh-plugin-export-overlays/rhdh-plugin-export-overlays/overlay-repo/workspaces/matomo/metadata

No E2E tests available for this workspace.