Skip to content

chore(mcp-integrations): bump workspace to Backstage 1.48.2#2405

Merged
johnmcollier merged 4 commits intoredhat-developer:mainfrom
johnmcollier:bs1482
Mar 2, 2026
Merged

chore(mcp-integrations): bump workspace to Backstage 1.48.2#2405
johnmcollier merged 4 commits intoredhat-developer:mainfrom
johnmcollier:bs1482

Conversation

@johnmcollier
Copy link
Member

@johnmcollier johnmcollier commented Feb 26, 2026

User description

Hey, I just made a Pull Request!

https://issues.redhat.com/browse/RHIDP-11969

Updates mcp-integrations to Backstage 1.48.2 via yarn backstage-cli versions:bump

✔️ Checklist

  • A changeset describing the change and affected packages. (more info)
  • Added or Updated documentation
  • Tests for new functionality and regression tests for bug fixes
  • Screenshots attached (for UI changes)

PR Type

Enhancement


Description

  • Update mcp-integrations workspace to Backstage 1.48.2

  • Bump all Backstage dependencies across packages and plugins

  • Update version in backstage.json from 1.47.3 to 1.48.3

  • Create changeset documenting patch updates for three MCP extras plugins


Diagram Walkthrough

flowchart LR
  A["Backstage 1.47.3"] -- "yarn backstage-cli versions:bump" --> B["Backstage 1.48.2"]
  B --> C["Update backstage.json"]
  B --> D["Update package.json dependencies"]
  B --> E["Create changeset"]
  D --> F["App package"]
  D --> G["Backend package"]
  D --> H["Plugin packages"]
Loading

File Walkthrough

Relevant files
Configuration changes
four-socks-flash.md
Add changeset for Backstage 1.48.2 update                               

workspaces/mcp-integrations/.changeset/four-socks-flash.md

  • Create new changeset file documenting workspace update
  • Mark three MCP extras plugins with patch version bumps
  • Document update to Backstage 1.48.2
+7/-0     
backstage.json
Update backstage.json version to 1.48.3                                   

workspaces/mcp-integrations/backstage.json

  • Update version from 1.47.3 to 1.48.3
  • Reformat JSON with proper indentation
+3/-1     
Dependencies
package.json
Update root workspace devDependencies                                       

workspaces/mcp-integrations/package.json

  • Bump @backstage/cli from 0.35.3 to 0.35.4
  • Bump @backstage/e2e-test-utils from 0.1.1 to 0.1.2
  • Bump @backstage/repo-tools from 0.16.3 to 0.16.5
+3/-3     
package.json
Update app package Backstage dependencies                               

workspaces/mcp-integrations/packages/app/package.json

  • Update 20+ @backstage dependencies to latest versions
  • Notable updates: plugin-catalog-react to 2.0.0, plugin-user-settings
    to 0.9.0
  • Update @backstage/test-utils from 1.7.14 to 1.7.15
+25/-25 
package.json
Update backend package Backstage dependencies                       

workspaces/mcp-integrations/packages/backend/package.json

  • Update 20+ @backstage backend plugin dependencies
  • Notable updates: plugin-auth-backend to 0.27.0, plugin-catalog-backend
    to 3.4.0
  • Update @backstage/cli from 0.35.3 to 0.35.4
+25/-25 
package.json
Update scaffolder-mcp-extras plugin dependencies                 

workspaces/mcp-integrations/plugins/scaffolder-mcp-extras/package.json

  • Update @backstage/backend-defaults from 0.15.1 to 0.15.2
  • Update @backstage/backend-plugin-api from 1.6.2 to 1.7.0
  • Update @backstage/catalog-client from 1.12.1 to 1.13.0
  • Update @backstage/plugin-catalog-node from 1.20.1 to 2.0.0
  • Update @backstage/backend-test-utils from 1.10.4 to 1.11.0
  • Update @backstage/cli from 0.35.3 to 0.35.4
+6/-6     
package.json
Update software-catalog-mcp-extras plugin dependencies     

workspaces/mcp-integrations/plugins/software-catalog-mcp-extras/package.json

  • Update @backstage/backend-defaults from 0.15.1 to 0.15.2
  • Update @backstage/backend-plugin-api from 1.6.2 to 1.7.0
  • Update @backstage/catalog-client from 1.12.1 to 1.13.0
  • Update @backstage/plugin-catalog-node from 1.20.1 to 2.0.0
  • Update @backstage/backend-test-utils from 1.10.4 to 1.11.0
  • Update @backstage/cli from 0.35.3 to 0.35.4
+6/-6     
package.json
Update techdocs-mcp-extras plugin dependencies                     

workspaces/mcp-integrations/plugins/techdocs-mcp-extras/package.json

  • Update @backstage/backend-defaults from 0.15.1 to 0.15.2
  • Update @backstage/backend-plugin-api from 1.6.2 to 1.7.0
  • Update @backstage/catalog-client from 1.12.1 to 1.13.0
  • Update @backstage/plugin-catalog-node from 1.20.1 to 2.0.0
  • Update @backstage/backend-test-utils from 1.10.4 to 1.11.0
  • Update @backstage/cli from 0.35.3 to 0.35.4
+6/-6     

Signed-off-by: John Collier <jcollier@redhat.com>
Signed-off-by: John Collier <jcollier@redhat.com>
@johnmcollier johnmcollier requested review from a team, gabemontero and thepetk as code owners February 26, 2026 21:56
@rhdh-gh-app
Copy link

rhdh-gh-app bot commented Feb 26, 2026

Changed Packages

Package Name Package Path Changeset Bump Current Version
app workspaces/mcp-integrations/packages/app none v0.0.0
backend workspaces/mcp-integrations/packages/backend none v0.0.0
@red-hat-developer-hub/backstage-plugin-scaffolder-mcp-extras workspaces/mcp-integrations/plugins/scaffolder-mcp-extras patch v0.2.0
@red-hat-developer-hub/backstage-plugin-software-catalog-mcp-extras workspaces/mcp-integrations/plugins/software-catalog-mcp-extras patch v0.2.0
@red-hat-developer-hub/backstage-plugin-techdocs-mcp-extras workspaces/mcp-integrations/plugins/techdocs-mcp-extras patch v0.2.0

@rhdh-qodo-merge
Copy link

rhdh-qodo-merge bot commented Feb 26, 2026

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢
No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
🎫 No ticket provided
  • Create ticket/issue
Codebase Duplication Compliance
🟢
No codebase code duplication found No new components were introduced in the PR code
Custom Compliance
🟢
Generic: Comprehensive Audit Trails

Objective: To create a detailed and reliable record of critical system actions for security analysis
and compliance.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Meaningful Naming and Self-Documenting Code

Objective: Ensure all identifiers clearly express their purpose and intent, making code
self-documenting

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Robust Error Handling and Edge Case Management

Objective: Ensure comprehensive error handling that provides meaningful context and graceful
degradation

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Secure Error Handling

Objective: To prevent the leakage of sensitive system information through error messages while
providing sufficient detail for internal debugging.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Secure Logging Practices

Objective: To ensure logs are useful for debugging and auditing without exposing sensitive
information like PII, PHI, or cardholder data.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Security-First Input Validation and Data Handling

Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent
vulnerabilities

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

  • Update
Compliance status legend 🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

@rhdh-qodo-merge
Copy link

rhdh-qodo-merge bot commented Feb 26, 2026

PR Code Suggestions ✨

Explore these optional code suggestions:

CategorySuggestion                                                                                                                                    Impact
Possible issue
Address breaking changes from major dependency upgrade

Review the release notes for @backstage/plugin-catalog-react@2.0.0 and apply any
necessary code migrations to address potential breaking changes from this major
version upgrade.

workspaces/mcp-integrations/packages/app/package.json [34]

+// No code change suggestion. This is a high-level concern.
+// Please review the release notes for `@backstage/plugin-catalog-react@2.0.0`
+// and apply necessary code migrations. The version bump itself is:
 "@backstage/plugin-catalog-react": "^2.0.0",
  • Apply / Chat
Suggestion importance[1-10]: 7

__

Why: The suggestion correctly identifies a major version bump for a dependency, which can introduce breaking changes, and rightly advises reviewing the release notes.

Medium
General
Fix inconsistent version number in changeset

Update the Backstage version in the changeset file from 1.48.2 to 1.48.3 to
match the version in backstage.json and ensure consistency.

workspaces/mcp-integrations/.changeset/four-socks-flash.md [7]

-Update workspace to Backstage 1.48.2
+Update workspace to Backstage 1.48.3
  • Apply / Chat
Suggestion importance[1-10]: 5

__

Why: The suggestion correctly identifies and proposes a fix for an inconsistency between the changeset file and the backstage.json version, improving documentation clarity.

Low
  • Update

Signed-off-by: John Collier <jcollier@redhat.com>
Copy link
Contributor

@gabemontero gabemontero left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cool

@johnmcollier johnmcollier reopened this Mar 2, 2026
@rhdh-qodo-merge
Copy link

Review Summary by Qodo

Upgrade mcp-integrations workspace to Backstage 1.48.2

✨ Enhancement

Grey Divider

Walkthroughs

Description
• Upgrade mcp-integrations workspace to Backstage 1.48.2
• Update all Backstage dependencies across packages and plugins
• Bump CLI and tooling versions to latest compatible releases
• Add changeset documenting patch version updates
Diagram
flowchart LR
  BS["Backstage 1.47.3"] -- "upgrade" --> BS2["Backstage 1.48.2"]
  BS2 -- "updates" --> PKG["Package Dependencies"]
  BS2 -- "updates" --> PLUGINS["Plugin Dependencies"]
  PKG -- "includes" --> CLI["CLI ^0.35.4"]
  PKG -- "includes" --> CORE["Core Libraries"]
  PLUGINS -- "includes" --> BACKEND["Backend Plugins"]
  PLUGINS -- "includes" --> CATALOG["Catalog Plugins"]
Loading

Grey Divider

File Changes

1. workspaces/mcp-integrations/.changeset/four-socks-flash.md 📝 Documentation +7/-0

Add changeset for Backstage 1.48.2 upgrade

• Create new changeset documenting workspace upgrade
• Mark three MCP plugin packages for patch version bump
• Document update to Backstage 1.48.2

workspaces/mcp-integrations/.changeset/four-socks-flash.md


2. workspaces/mcp-integrations/backstage.json ⚙️ Configuration changes +3/-1

Update Backstage version to 1.48.3

• Update version from 1.47.3 to 1.48.3
• Reformat JSON with proper indentation

workspaces/mcp-integrations/backstage.json


3. workspaces/mcp-integrations/package.json Dependencies +3/-3

Update root workspace dev dependencies

• Bump @backstage/cli from ^0.35.3 to ^0.35.4
• Bump @backstage/e2e-test-utils from ^0.1.1 to ^0.1.2
• Bump @backstage/repo-tools from ^0.16.3 to ^0.16.5

workspaces/mcp-integrations/package.json


View more (5)
4. workspaces/mcp-integrations/packages/app/package.json Dependencies +25/-25

Update frontend app Backstage dependencies

• Update 30+ Backstage core and plugin dependencies
• Bump app-defaults, core-app-api, core-components versions
• Update plugin-catalog-react to major version 2.0.0
• Bump theme and UI library versions

workspaces/mcp-integrations/packages/app/package.json


5. workspaces/mcp-integrations/packages/backend/package.json Dependencies +25/-25

Update backend package Backstage dependencies

• Update 30+ Backstage backend plugin dependencies
• Bump backend-defaults, auth-backend, catalog-backend versions
• Update plugin-auth-backend-module-github-provider to ^0.5.0
• Bump CLI and search backend module versions

workspaces/mcp-integrations/packages/backend/package.json


6. workspaces/mcp-integrations/plugins/scaffolder-mcp-extras/package.json Dependencies +6/-6

Update scaffolder plugin dependencies

• Update backend-defaults from ^0.15.1 to ^0.15.2
• Bump backend-plugin-api from ^1.6.2 to ^1.7.0
• Update catalog-client from ^1.12.1 to ^1.13.0
• Bump plugin-catalog-node to major version ^2.0.0
• Update backend-test-utils and CLI versions

workspaces/mcp-integrations/plugins/scaffolder-mcp-extras/package.json


7. workspaces/mcp-integrations/plugins/software-catalog-mcp-extras/package.json Dependencies +6/-6

Update software catalog plugin dependencies

• Update backend-defaults from ^0.15.1 to ^0.15.2
• Bump backend-plugin-api from ^1.6.2 to ^1.7.0
• Update catalog-client from ^1.12.1 to ^1.13.0
• Bump plugin-catalog-node to major version ^2.0.0
• Update backend-test-utils and CLI versions

workspaces/mcp-integrations/plugins/software-catalog-mcp-extras/package.json


8. workspaces/mcp-integrations/plugins/techdocs-mcp-extras/package.json Dependencies +6/-6

Update techdocs plugin dependencies

• Update backend-defaults from ^0.15.1 to ^0.15.2
• Bump backend-plugin-api from ^1.6.2 to ^1.7.0
• Update catalog-client from ^1.12.1 to ^1.13.0
• Bump plugin-catalog-node to major version ^2.0.0
• Update backend-test-utils and CLI versions

workspaces/mcp-integrations/plugins/techdocs-mcp-extras/package.json


Grey Divider

Qodo Logo

@rhdh-qodo-merge
Copy link

rhdh-qodo-merge bot commented Mar 2, 2026

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📎 Requirement gaps (0)

Grey Divider


Action required

1. Backstage version mismatch 🐞 Bug ✓ Correctness
Description
workspaces/mcp-integrations/backstage.json now reports Backstage 1.48.3 while the changeset text
says the workspace was updated to Backstage 1.48.2. Multiple repo scripts read
backstage.json.version for CI outputs and compatibility dashboards/badges, so the mismatch will
publish misleading compatibility info.
Code

workspaces/mcp-integrations/backstage.json[R1-3]

+{
+  "version": "1.48.3"
+}
Evidence
The workspace source-of-truth version is workspaces/<workspace>/backstage.json. In this PR it is
set to 1.48.3, but the accompanying changeset states 1.48.2. Repo automation (CI outputs, upgrade
dashboard, and compatibility badge generator) reads backstage.json.version, so an incorrect value
will propagate into release metadata and reporting.

workspaces/mcp-integrations/backstage.json[1-3]
workspaces/mcp-integrations/.changeset/four-socks-flash.md[1-7]
scripts/ci/set-release-name.js[24-30]
scripts/generate-upgrade-dashboard.js[43-60]
scripts/list-compatibility.js[39-43]
workspaces/mcp-integrations/README.md[13-20]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`workspaces/mcp-integrations/backstage.json` declares Backstage version `1.48.3`, but the workspace changeset text says `1.48.2`. Repo CI/reporting scripts consume `backstage.json.version`, so this mismatch will propagate incorrect compatibility information.

## Issue Context
- `backstage.json` is treated as the workspace&#x27;s compatibility/version source for CI outputs and dashboards.
- The changeset message is user-facing release metadata; it should match the actual declared compatibility version.

## Fix Focus Areas
- workspaces/mcp-integrations/backstage.json[1-3]
- workspaces/mcp-integrations/.changeset/four-socks-flash.md[1-7]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

ⓘ The new review experience is currently in Beta. Learn more

Grey Divider

Qodo Logo

Comment on lines +1 to +3
{
"version": "1.48.3"
}

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Action required

1. Backstage version mismatch 🐞 Bug ✓ Correctness

workspaces/mcp-integrations/backstage.json now reports Backstage 1.48.3 while the changeset text
says the workspace was updated to Backstage 1.48.2. Multiple repo scripts read
backstage.json.version for CI outputs and compatibility dashboards/badges, so the mismatch will
publish misleading compatibility info.
Agent Prompt
## Issue description
`workspaces/mcp-integrations/backstage.json` declares Backstage version `1.48.3`, but the workspace changeset text says `1.48.2`. Repo CI/reporting scripts consume `backstage.json.version`, so this mismatch will propagate incorrect compatibility information.

## Issue Context
- `backstage.json` is treated as the workspace's compatibility/version source for CI outputs and dashboards.
- The changeset message is user-facing release metadata; it should match the actual declared compatibility version.

## Fix Focus Areas
- workspaces/mcp-integrations/backstage.json[1-3]
- workspaces/mcp-integrations/.changeset/four-socks-flash.md[1-7]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

…bs1482

Signed-off-by: John Collier <jcollier@redhat.com>
@johnmcollier
Copy link
Member Author

Rebasing before merging

@sonarqubecloud
Copy link

sonarqubecloud bot commented Mar 2, 2026

@johnmcollier johnmcollier merged commit c10e18a into redhat-developer:main Mar 2, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants