fix(scorecard): remove redundant /alpha re-export of translations

[its-mitesh-kumar]

Description

Removes the redundant /alpha re-export of translations (scorecardTranslationRef, scorecardTranslations) from the scorecard plugin. After PR #3953 (RHIDP-14416) promoted the scorecard NFS plugin from /alpha to stable, translations were already exported from the main entry point (src/index.ts). The /alpha re-export in src/alpha.ts was misleading, making it appear translations were still an alpha feature.

This change deletes src/alpha.ts entirely (it had no other exports), removes the ./alpha entry point from package.json exports/typesVersions, and deletes the now-unnecessary report-alpha.api.md API report.

Root cause

src/alpha.ts contained export * from './translations' which duplicated the stable exports in src/index.ts. No code in the repository imports from the /alpha path — the only reference was in README.md as a migration example showing the old import path.

Fixed

• RHDHBUGS-3522 — Remove redundant /alpha re-export of translations from scorecard plugin

Test Plan

• Verify src/index.ts still exports scorecardTranslationRef and scorecardTranslations
• Verify no TypeScript compilation errors in the scorecard workspace
• Verify no imports reference the removed /alpha entry point
• Verify API reports are up to date (no report-alpha.api.md needed)

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)

Note

This bug fix was identified and implemented using the bug-fix and raise-pr agent skills. Please verify the fix thoroughly before merging.

Made with Cursor

[rhdh-gh-app]

Changed Packages

Package Name	Package Path	Changeset Bump	Current Version
@red-hat-developer-hub/backstage-plugin-scorecard	workspaces/scorecard/plugins/scorecard	patch	v3.0.0

[rhdh-qodo-merge]

PR Summary by Qodo

Fix scorecard plugin: remove redundant /alpha translation entrypoint

🐞 Bug fix ⚙️ Configuration changes 🕐 10-20 Minutes

AI Description

• Removes misleading /alpha translation re-exports now that scorecard is stable.
• Drops the ./alpha package entrypoint from exports/typesVersions and related API surface.
• Adds a changeset and refreshes API Extractor reports to match the new public API.

Diagram

graph TD
  C["Downstream consumers"] --> P["scorecard package (.)"] --> I["src/index.ts"] --> T["translations exports"]
  P --> PJ["package.json exports/typesVersions"] --> AR["API Extractor reports"]
  PJ -. removes .-> A["/alpha entrypoint"]

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Keep `/alpha` as deprecated alias

• ➕ Avoids breaking any external consumers still importing .../alpha
• ➕ Provides a clearer migration window and can be paired with deprecation docs
• ➖ Continues to imply /alpha is a supported surface
• ➖ Requires maintaining the extra entrypoint and (likely) its API report/artifacts

2. Replace `/alpha` with a runtime error stub

• ➕ Makes the breaking change explicit with a clear message if someone imports it
• ➖ Still ships and maintains an entrypoint solely to fail
• ➖ Adds noise/complexity compared to simply removing the export

Recommendation: Current approach (remove the /alpha entrypoint entirely) is appropriate if the project intends /alpha to be unsupported going forward and internal usage is confirmed absent. If there is concern about external downstream breakage, the best alternative is a deprecation-period alias (retain ./alpha re-export marked deprecated) for one release before removal.

Files changed (3) +9 / -12

Bug fix (1) +0 / -4

package.jsonRemove './alpha' export and TypeScript typesVersions mapping +0/-4

Remove './alpha' export and TypeScript typesVersions mapping

• Deletes the './alpha' entry from 'exports' and removes the corresponding 'typesVersions' mapping so consumers can no longer import from the '/alpha' subpath.

workspaces/scorecard/plugins/scorecard/package.json

Documentation (1) +4 / -8

report.api.mdRefresh stable API report after entrypoint cleanup +4/-8

Refresh stable API report after entrypoint cleanup

• Updates the generated API report to reflect the current stable public API after removing the '/alpha' entrypoint and regenerating reports (includes minor ordering/formatting changes).

workspaces/scorecard/plugins/scorecard/report.api.md

Other (1) +5 / -0

clean-tigers-rest.mdAdd patch changeset documenting '/alpha' translation export removal +5/-0

Add patch changeset documenting '/alpha' translation export removal

• Introduces a patch changeset for the scorecard plugin noting that translations are available via the main entrypoint and the '/alpha' re-export was removed.

workspaces/scorecard/.changeset/clean-tigers-rest.md

[fullsend-ai-review]

🤖 Review · ⚠️ Cancelled · Started 4:37 AM UTC · Ended 4:48 AM UTC
Commit: 6338cdd · View workflow run →

[rhdh-qodo-merge]

Code Review by Qodo

🐞 Bugs (2) 📘 Rule violations (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)

Context used

⚠️ Tickets: not configured — ticket URL found in PR but could not be fetched — check ticket provider credentials

✅ Compliance rules (platform): 11 rules

✅ Cross-repo context

  Explored: repo: redhat-developer/rhdh (sha: ddfe8d07)

  Explored: repo: redhat-developer/rhdh-local (sha: 2ae9e8c8)

  Not relevant to this PR: redhat-developer/rhdh-chart

  Not relevant to this PR: redhat-developer/rhdh-operator

1. README still advertises /alpha 🐞 Bug ⚙ Maintainability

Description

The PR removes the ./alpha export entry point, but the Scorecard README still states that
translations remain available at ./alpha, which will direct users to an import path that no longer
resolves. This creates immediate documentation-driven install/migration failures for consumers
following the README.

Code

workspaces/scorecard/plugins/scorecard/package.json[9]

-    "./alpha": "./src/alpha.ts",

Relevance

●●● Strong

They previously accepted updating Scorecard README/docs to reflect correct import paths/exports
after subpath changes.

PR-#3953

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

./alpha is removed from the package export map, while the README still claims translations remain
available at ./alpha; the main entrypoint still exports the translation symbols, so the doc should
point there instead.

workspaces/scorecard/plugins/scorecard/package.json[7-20]
workspaces/scorecard/plugins/scorecard/README.md[1-6]
workspaces/scorecard/plugins/scorecard/src/index.ts[84-92]

Agent prompt

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

### Issue description
The package no longer exports `@red-hat-developer-hub/backstage-plugin-scorecard/alpha`, but the README still claims translations are available at `./alpha`.

### Issue Context
`./alpha` was removed from `package.json` exports/typesVersions; translations are still exported from the main entry point.

### Fix Focus Areas
- workspaces/scorecard/plugins/scorecard/README.md[1-10]
- workspaces/scorecard/plugins/scorecard/package.json[7-20]
- workspaces/scorecard/plugins/scorecard/src/index.ts[84-92]

### Expected change
Update README wording to indicate translations are available from the main entry point (and remove the statement that they remain at `./alpha`).

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

---

2. Breaking change labeled patch 🐞 Bug ☼ Reliability

Description

The changeset declares a patch bump, but this PR removes a published package subpath export
(./alpha) which will break any downstream importing
@red-hat-developer-hub/backstage-plugin-scorecard/alpha. This conflicts with the repo’s stated
semantic versioning approach and can cause unexpected build/runtime failures on patch upgrade.

Code

workspaces/scorecard/.changeset/clean-tigers-rest.md[2]

+'@red-hat-developer-hub/backstage-plugin-scorecard': patch

Relevance

●●● Strong

Team has precedent adjusting changeset bump/marking BREAKING when public API changes are
semver-breaking.

PR-#3953
PR-#3417

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The changeset is explicitly patch, while package.json no longer exports ./alpha;
CONTRIBUTING.md states semantic versioning is enforced through Changesets, making a patch release
risky for a breaking removal.

workspaces/scorecard/.changeset/clean-tigers-rest.md[1-5]
workspaces/scorecard/plugins/scorecard/package.json[7-20]
CONTRIBUTING.md[83-90]

Agent prompt

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

### Issue description
The changeset marks this as a `patch`, but the PR removes the `./alpha` export path, which is a breaking public API change for any consumer still using that subpath.

### Issue Context
Repo CONTRIBUTING states packages follow semantic versioning via Changesets.

### Fix Focus Areas
- workspaces/scorecard/.changeset/clean-tigers-rest.md[1-5]
- workspaces/scorecard/plugins/scorecard/package.json[7-20]
- CONTRIBUTING.md[83-90]

### Expected change
Either:
1) Change the changeset to a `major` bump (or otherwise align with your semver policy), and explicitly note the breaking removal of the `/alpha` entrypoint; OR
2) Re-introduce `./alpha` as a compatibility alias (deprecated) and keep the patch bump.

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

---

_{To customize comments, go to the Qodo configuration screen, or learn more in the docs.}

[sonarqubecloud]

Quality Gate passed

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

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 4:49 AM UTC · Completed 5:06 AM UTC
Commit: c66ac1d · View workflow run →

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 57.93%. Comparing base (674b95a) to head (c66ac1d).
⚠️ Report is 213 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #4095   +/-   ##
=======================================
  Coverage   57.93%   57.93%           
=======================================
  Files        2396     2396           
  Lines       96104    96104           
  Branches    26845    26852    +7     
=======================================
  Hits        55675    55675           
  Misses      40223    40223           
  Partials      206      206           

Flag	Coverage Δ		*Carryforward flag
adoption-insights	84.54% <ø> (ø)		Carriedforward from 674b95a
ai-integrations	69.06% <ø> (ø)		Carriedforward from 674b95a
app-defaults	69.79% <ø> (ø)		Carriedforward from 674b95a
augment	46.67% <ø> (ø)		Carriedforward from 674b95a
boost	76.77% <ø> (ø)		Carriedforward from 674b95a
bulk-import	72.55% <ø> (ø)		Carriedforward from 674b95a
cost-management	13.55% <ø> (ø)		Carriedforward from 674b95a
dcm	60.72% <ø> (ø)		Carriedforward from 674b95a
extensions	56.48% <ø> (ø)		Carriedforward from 674b95a
global-floating-action-button	71.18% <ø> (ø)		Carriedforward from 674b95a
global-header	62.17% <ø> (ø)		Carriedforward from 674b95a
homepage	47.54% <ø> (ø)		Carriedforward from 674b95a
install-dynamic-plugins	56.77% <ø> (ø)		Carriedforward from 674b95a
intelligent-assistant	74.53% <ø> (ø)		Carriedforward from 674b95a
konflux	91.98% <ø> (ø)		Carriedforward from 674b95a
lightspeed	69.02% <ø> (ø)		Carriedforward from 674b95a
mcp-integrations	83.40% <ø> (ø)		Carriedforward from 674b95a
orchestrator	66.79% <ø> (ø)		Carriedforward from 674b95a
quickstart	65.04% <ø> (ø)		Carriedforward from 674b95a
sandbox	79.56% <ø> (ø)		Carriedforward from 674b95a
scorecard	85.34% <ø> (ø)
theme	87.90% <ø> (ø)		Carriedforward from 674b95a
translations	5.12% <ø> (ø)		Carriedforward from 674b95a
x2a	79.31% <ø> (ø)		Carriedforward from 674b95a

*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 674b95a...c66ac1d. 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.

[fullsend-ai-review]

Review

Findings

High

• [stale-documentation] workspaces/scorecard/plugins/scorecard/README.md:5 — Line 5 states "Translations remain available at ./alpha." This PR removes the ./alpha export path and deletes src/alpha.ts. After this change, the statement is false and will mislead users into importing from a path that no longer resolves.
  Remediation: Remove or update the sentence. Replace with "Translations are exported from the main entry point." or simply remove it.

Medium

• [breaking-change] workspaces/scorecard/plugins/scorecard/package.json:9 — Removing the ./alpha export entry point removes a documented import path. The 3.0.0 CHANGELOG stated "translations remain at ./alpha", creating a contract consumers could rely on. Any consumer using import { ... } from '@red-hat-developer-hub/backstage-plugin-scorecard/alpha' will get a module-not-found error after upgrading. The symbols are still available from the main entry point, so this is a path removal rather than a functional API break.
  Remediation: Change the changeset from patch to minor at minimum. If external consumers may be using the /alpha path, use major instead.

• [semver-classification] workspaces/scorecard/.changeset/clean-tigers-rest.md:2 — The changeset classifies this as patch, but removing a public export path is not a bug fix. It should be at least minor since it removes a documented (though transitional) import path.
  Remediation: Change the changeset from patch to minor, or major if the team believes external consumers actively use the /alpha path.

Low

• [stale-documentation] workspaces/scorecard/plugins/scorecard/README.md:286 — The migration notes section shows the old /alpha import path. The guidance already directs users away from /alpha and remains directionally correct, but a note that /alpha has been fully removed would improve clarity.

• [documentation-contract-mismatch] workspaces/scorecard/plugins/scorecard/CHANGELOG.md:9 — The 3.0.0 CHANGELOG states "translations remain at ./alpha". This is a historical record correct for 3.0.0. The changeset for this PR already describes the removal, which will generate a new CHANGELOG entry.

• [stale-reference] workspaces/scorecard/.prettierignore:11 — The deleted report-alpha.api.md is still referenced in .prettierignore. This is harmless (prettierignore silently skips non-existent files) but is a cleanup oversight.

---

Labels: PR modifies translation export paths in the scorecard plugin

[fullsend-ai-review]

See the review comment for full details.

[fullsend-ai-review]

[medium] breaking-change

Removing the ./alpha export entry point removes a documented import path. The 3.0.0 CHANGELOG stated 'translations remain at ./alpha', creating a contract consumers could rely on. Any consumer using the /alpha import path will get a module-not-found error after upgrading. The symbols are still available from the main entry point, so this is a path removal rather than a functional API break.

Suggested fix: Change the changeset from patch to minor at minimum. If external consumers may be using the /alpha path, use major instead.

[fullsend-ai-review]

[medium] semver-classification

The changeset classifies this as a patch change, but removing a public export path is not a bug fix. It should be at least minor since it removes a documented (though transitional) import path.

Suggested fix: Change the changeset from patch to minor, or major if the team believes external consumers actively use the /alpha path.

[its-mitesh-kumar]

I have not verified the PR, please feel free to verify and merge. I will be deleting this comment once verified.

[github-actions]

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!