Skip to content

[release-1.10] chore: bump backstage/errors to 1.3.0#5039

Draft
04kash wants to merge 2 commits into
redhat-developer:release-1.10from
04kash:bump-errors-1.10
Draft

[release-1.10] chore: bump backstage/errors to 1.3.0#5039
04kash wants to merge 2 commits into
redhat-developer:release-1.10from
04kash:bump-errors-1.10

Conversation

@04kash

@04kash 04kash commented Jun 30, 2026

Copy link
Copy Markdown
Member

Description

RHDH 1.10 is on Backstage 1.49.4, so the RHDH backend provides @backstage/errors 1.2.7. We were pulling in @backstage/plugin-techdocs-node 1.14.5, which calls toError (added in errors 1.3.0). techdocs-node is bundled into the dynamic plugin, but @backstage/errors is a peerDep — it's not bundled, the RHDH backend provides it at runtime. So techdocs-node's ^1.3.0 declaration only affects the build workspace; it doesn't upgrade what the backend actually loads.

1.14.5 came in through global-header's caret on @backstage/plugin-search-backend-module-techdocs. Yarn resolved that to 0.4.13, which depends on techdocs-node ^1.14.5, and deduped it with the techdocs wrapper's 0.4.12 pin. techdocs-node 1.14.5 did bump its @backstage/errors minimum correctly (backstage/backstage#33720); the problem is the RHDH backend still serves 1.2.7.

This PR bumps @backstage/errors to 1.3.0 to pull in the toError function. (with yarn up @backstage/errors@1.3.0 and yarn dedupe @backstage/errors)

Alternative is to pin techdocs-node: #4962

Which issue(s) does this PR fix

PR acceptance criteria

Please make sure that the following steps are complete:

  • GitHub Actions are completed and successful
  • Unit Tests are updated and passing
  • E2E Tests are updated and passing
  • Documentation is updated if necessary (requirement for new features)
  • Add a screenshot if the change is UX/UI related

How to test changes / Special notes to the reviewer

Signed-off-by: Kashish Mittal <kmittal@redhat.com>
@openshift-ci

openshift-ci Bot commented Jun 30, 2026

Copy link
Copy Markdown

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@codecov

codecov Bot commented Jun 30, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.24%. Comparing base (6f9b521) to head (f4984a3).

Additional details and impacted files
@@                Coverage Diff                @@
##           release-1.10    #5039       +/-   ##
=================================================
+ Coverage         41.03%   69.24%   +28.21%     
=================================================
  Files               121      123        +2     
  Lines              2220     4920     +2700     
  Branches            563      563               
=================================================
+ Hits                911     3407     +2496     
- Misses             1303     1508      +205     
+ Partials              6        5        -1     
Flag Coverage Δ
install-dynamic-plugins 92.44% <ø> (?)
rhdh 41.03% <ø> (ø)

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 6f9b521...f4984a3. 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.

@github-actions

Copy link
Copy Markdown
Contributor

Image was built and published successfully. It is available at:

@sonarqubecloud

sonarqubecloud Bot commented Jul 2, 2026

Copy link
Copy Markdown

@github-actions

github-actions Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Image was built and published successfully. It is available at:

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.

1 participant