fix(homepage): fix missing translations for homepage card widgets

[debsmita1]

Hey, I just made a Pull Request!

Resolves:
https://redhat.atlassian.net/browse/RHDHBUGS-3271

Screen.Recording.2026-06-25.at.4.26.37.PM.mov

✔️ 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)

[rhdh-gh-app]

Changed Packages

Package Name	Package Path	Changeset Bump	Current Version
app-legacy	workspaces/homepage/packages/app-legacy	none	v0.0.0
@red-hat-developer-hub/backstage-plugin-homepage	workspaces/homepage/plugins/homepage	patch	v1.15.0

[codecov]

Codecov Report

❌ Patch coverage is 58.03571% with 47 lines in your changes missing coverage. Please review.
✅ Project coverage is 54.11%. Comparing base (d69d6d6) to head (992648a).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3575      +/-   ##
==========================================
- Coverage   54.28%   54.11%   -0.18%     
==========================================
  Files        2347     2301      -46     
  Lines       89650    87955    -1695     
  Branches    25020    24541     -479     
==========================================
- Hits        48666    47594    -1072     
+ Misses      39456    38797     -659     
- Partials     1528     1564      +36     

Flag	Coverage Δ		*Carryforward flag
adoption-insights	83.70% <ø> (ø)		Carriedforward from d698e30
ai-integrations	68.16% <ø> (-0.19%)	⬇️	Carriedforward from d698e30
app-defaults	69.79% <ø> (ø)		Carriedforward from d698e30
augment	46.39% <ø> (ø)		Carriedforward from d698e30
boost	73.96% <ø> (-0.73%)	⬇️	Carriedforward from d698e30
bulk-import	72.46% <ø> (ø)		Carriedforward from d698e30
cost-management	14.10% <ø> (ø)		Carriedforward from d698e30
dcm	61.70% <ø> (-0.11%)	⬇️	Carriedforward from d698e30
extensions	61.53% <ø> (ø)		Carriedforward from d698e30
global-floating-action-button	71.18% <ø> (ø)		Carriedforward from d698e30
global-header	59.71% <ø> (ø)		Carriedforward from d698e30
homepage	50.51% <58.03%> (+0.28%)	⬆️
install-dynamic-plugins	56.77% <ø> (ø)		Carriedforward from d698e30
konflux	91.49% <ø> (ø)		Carriedforward from d698e30
lightspeed	68.58% <ø> (-0.24%)	⬇️	Carriedforward from d698e30
mcp-integrations	85.46% <ø> (ø)		Carriedforward from d698e30
orchestrator	38.30% <ø> (-1.18%)	⬇️	Carriedforward from d698e30
quickstart	63.76% <ø> (-1.87%)	⬇️	Carriedforward from d698e30
sandbox	79.56% <ø> (ø)		Carriedforward from d698e30
scorecard	83.96% <ø> (+1.29%)	⬆️	Carriedforward from d698e30
theme	61.26% <ø> (ø)		Carriedforward from d698e30
translations	7.25% <ø> (ø)		Carriedforward from d698e30
x2a	78.68% <ø> (ø)		Carriedforward from d698e30

*This pull request uses carry forward flags. Click here to find out more.

---

Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d69d6d6...992648a. Read the comment docs.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[sonarqubecloud]

Quality Gate passed

Issues
3 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

[its-mitesh-kumar]

Hey @debsmita1, nice work on the i18n coverage and tests!

Two concerns about the updateWidgetComponentData approach:

1. Coupling to Backstage internals — We're directly mutating __backstage_data, an undocumented internal of @backstage/core-plugin-api. If upstream renames/restructures this, our translations silently break with zero errors.

2. Magic string sync — widgetTranslationKeysByName maps names like 'Red Hat Developer Hub - Onboarding' to translation keys. These must stay manually in sync with params.name in homePageCards.tsx. A rename = silent i18n breakage.

Upstream proposal: The root cause is HomePageWidgetBlueprint only accepts plain string for title. Could we push upstream for a titleKey/descriptionKey field, where the renderer just calls t(titleKey) at render time? No internals mutation needed:

// Proposed upstream API
HomePageWidgetBlueprint.make({
  params: {
    titleKey: 'recentlyVisited.title',
    descriptionKey: 'recentlyVisited.description',
  }
})