Skip to content

Update roadie-backstage-plugins workspace to commit ba4ea07 for backstage 1.40.2 on branch main #1559

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
github-actions wants to merge 6 commits into
base: main
Choose a base branch
from
Open

Update roadie-backstage-plugins workspace to commit ba4ea07 for backstage 1.40.2 on branch main #1559

github-actions wants to merge 6 commits into from

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Oct 13, 2025 •
edited
Loading

Update roadie-backstage-plugins workspace at commit RoadieHQ/roadie-backstage-plugins@ba4ea07 for backstage 1.40.2 on branch main.

This PR was created automatically.

⚠️ Manual re-approval required
An override exists at workspaces/roadie-backstage-plugins/backstage.json. This upgrade is a Best-Effort match.
Since the previous version was manually verified to work against the target Backstage version, please review and test again before merging.
Click on the following link to see the source diff it introduces: RoadieHQ/roadie-backstage-plugins@c9f6296...ba4ea07.

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 github-actions bot requested review from a team, gashcrumb and kadel as code owners October 13, 2025 19:50
@github-actions github-actions bot added mandatory-workspace PR affects a workspace with required plugins for releases workspace-update PR modifies files in an existing workspace labels Oct 13, 2025
@davidfestal
Copy link
Member

davidfestal commented Oct 14, 2025

/publish

@github-actions
Copy link
Contributor Author

github-actions bot commented Oct 14, 2025

Publish workflow has completed with failure.

@github-actions
Copy link
Contributor Author

github-actions bot commented Oct 20, 2025

A new workspace commit b07bd946af6dfe5b0df57d815118d5319cb549e3 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
Copy link
Contributor Author

github-actions bot commented Nov 20, 2025

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

@github-actions github-actions bot added the stale label Nov 20, 2025
@davidfestal
Copy link
Member

davidfestal commented Dec 1, 2025

/update-commit

@github-actions
Copy link
Contributor Author

github-actions bot commented Dec 1, 2025

Update Commit workflow has completed with failure.

@davidfestal
Copy link
Member

davidfestal commented Dec 1, 2025

/update-commit

@github-actions github-actions bot changed the title Update roadie-backstage-plugins workspace to commit 794d6da for backstage 1.40.2 on branch main Update roadie-backstage-plugins workspace to commit ba4ea07 for backstage 1.40.2 on branch main Dec 1, 2025
@github-actions
Copy link
Contributor Author

github-actions bot commented Dec 1, 2025

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
Copy link
Contributor Author

github-actions bot commented Dec 1, 2025

Update Commit workflow has completed with success.

@davidfestal
Comment out automatically-proposed new plugins in plugins-list.yaml
878c6d4 
Comment out automatically-proposed new plugins in `plugins-list.yaml`
@davidfestal
Copy link
Member

davidfestal commented Dec 1, 2025

/publish

@github-actions
Copy link
Contributor Author

github-actions bot commented Dec 1, 2025

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/roadie-backstage-plugins 1.40.2 ⚪ 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/roadiehq-backstage-plugin-argo-cd-backend:pr_1559__4.4.2
    • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/roadiehq-backstage-plugin-argo-cd:pr_1559__2.11.0
    • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/roadiehq-backstage-plugin-datadog:pr_1559__2.5.0
    • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/roadiehq-backstage-plugin-github-insights:pr_1559__3.2.0
    • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/roadiehq-backstage-plugin-github-pull-requests:pr_1559__3.5.3
    • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/roadiehq-backstage-plugin-jira:pr_1559__2.13.1
    • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/roadiehq-backstage-plugin-security-insights:pr_1559__3.2.0
    • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/roadiehq-scaffolder-backend-argocd:pr_1559__1.7.1
    • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/roadiehq-scaffolder-backend-module-http-request:pr_1559__5.4.2
    • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/roadiehq-scaffolder-backend-module-utils:pr_1559__4.0.4

@davidfestal
Copy link
Member

davidfestal commented Dec 3, 2025

/publish

@github-actions
Copy link
Contributor Author

github-actions bot commented Dec 3, 2025

Publish workflow has completed with success.

Backstage Compatibility Check

✅ All workspaces are compatible with the target Backstage version (1.42.5).

No action required.

  • Published container images:
    • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/roadiehq-backstage-plugin-argo-cd-backend:pr_1559__4.4.2
    • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/roadiehq-backstage-plugin-argo-cd:pr_1559__2.11.0
    • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/roadiehq-backstage-plugin-datadog:pr_1559__2.5.0
    • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/roadiehq-backstage-plugin-github-insights:pr_1559__3.2.0
    • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/roadiehq-backstage-plugin-github-pull-requests:pr_1559__3.5.3
    • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/roadiehq-backstage-plugin-jira:pr_1559__2.13.1
    • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/roadiehq-backstage-plugin-security-insights:pr_1559__3.2.0
    • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/roadiehq-scaffolder-backend-argocd:pr_1559__1.7.1
    • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/roadiehq-scaffolder-backend-module-http-request:pr_1559__5.4.2
    • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/roadiehq-scaffolder-backend-module-utils:pr_1559__4.0.4

@github-actions
Copy link
Contributor Author

github-actions bot commented Dec 3, 2025

⚠️
Test workflow skipped because some plugin metadata files (<workspace>/metadata/*.yaml) were not found.

Add the corresponding metadata files to enable testing for this workspace.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@gashcrumb gashcrumb Awaiting requested review from gashcrumb gashcrumb is a code owner

@kadel kadel Awaiting requested review from kadel kadel is a code owner

Assignees

No one assigned

Labels

do-not-merge/hold mandatory-workspace PR affects a workspace with required plugins for releases stale workspace-update PR modifies files in an existing workspace

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@davidfestal @polasudo