Skip to content

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Oct 31, 2025

Update mcp-chat workspace at commit backstage/community-plugins@50a0659 for backstage 1.42.0 on branch main.

This PR was created automatically.
Click on the following link to see the source diff it introduces: backstage/community-plugins@8895c3c...50a0659.

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 31, 2025 19:47
@github-actions github-actions bot added the workspace-update PR modifies files in an existing workspace label Nov 1, 2025
@github-actions
Copy link
Contributor Author

A new workspace commit 2a437e90faed00fc8071de8dc387e3319c3e181a has been discovered (match type: 'exact').
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.

@christoph-jerolimov
Copy link
Member

/update-commit

@github-actions github-actions bot changed the title Update mcp-chat workspace to commit 873674b for backstage 1.42.0 on branch main Update mcp-chat workspace to commit 2a437e9 for backstage 1.42.0 on branch main Nov 25, 2025
@github-actions
Copy link
Contributor Author

Update Commit workflow has completed with success.

@christoph-jerolimov
Copy link
Member

/publish

@github-actions
Copy link
Contributor Author

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/backstage-community-plugin-mcp-chat:pr_1595__0.1.1
    • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-mcp-chat-backend:pr_1595__0.3.0

@github-actions
Copy link
Contributor Author

Test workflow passed. All plugins loaded successfully.

@github-actions
Copy link
Contributor Author

A new workspace commit 50a0659b419f42a301fd7825d4b55e0c9d1eaaf5 has been discovered (match type: 'exact').
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.

@Lucifergene
Copy link
Member

/update-commit

@github-actions github-actions bot changed the title Update mcp-chat workspace to commit 2a437e9 for backstage 1.42.0 on branch main Update mcp-chat workspace to commit 50a0659 for backstage 1.42.0 on branch main Dec 1, 2025
@github-actions
Copy link
Contributor Author

github-actions bot commented Dec 1, 2025

Update Commit workflow has completed with success.

@Lucifergene
Copy link
Member

/publish

@github-actions
Copy link
Contributor Author

github-actions bot commented Dec 1, 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/backstage-community-plugin-mcp-chat:pr_1595__0.1.1
    • ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-mcp-chat-backend:pr_1595__0.4.0

@github-actions
Copy link
Contributor Author

github-actions bot commented Dec 1, 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

Labels

workspace-update PR modifies files in an existing workspace

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants