Add rollbar workspace to commit 4e61224 for backstage 1.40.2 on branch main

[github-actions]

Add rollbar workspace at commit backstage/community-plugins@4e61224 for backstage 1.40.2 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.40.2. 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.40.2. 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 5812428

[github-actions]

A new workspace commit a85417c6ae16d138e01f88c921094432c91f6a10 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.

[github-actions]

A new workspace commit 4e612241829a42ae652fe0c2a1e94ae1e55e6378 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.

[github-actions]

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

[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.