Skip to content

chore(adoption-insights): version bump to v1.51.2#3403

Closed
Eswaraiahsapram wants to merge 7 commits into
redhat-developer:mainfrom
Eswaraiahsapram:adoption-insights-bump-1.51.2
Closed

chore(adoption-insights): version bump to v1.51.2#3403
Eswaraiahsapram wants to merge 7 commits into
redhat-developer:mainfrom
Eswaraiahsapram:adoption-insights-bump-1.51.2

Conversation

@Eswaraiahsapram

@Eswaraiahsapram Eswaraiahsapram commented Jun 16, 2026

Copy link
Copy Markdown
Member

Hey, I just made a Pull Request!

Adoption Insights backstage version bump

Fix - https://redhat.atlassian.net/browse/RHIDP-13789

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

rhdh-gh-app Bot commented Jun 16, 2026

Copy link
Copy Markdown

Important

This PR includes changes that affect public-facing API. Please ensure you are adding/updating documentation for new features or behavior.

Changed Packages

Package Name Package Path Changeset Bump Current Version
app-legacy workspaces/adoption-insights/packages/app-legacy none v0.0.0
app workspaces/adoption-insights/packages/app none v0.0.0
backend workspaces/adoption-insights/packages/backend none v0.0.0
@red-hat-developer-hub/backstage-plugin-adoption-insights-backend workspaces/adoption-insights/plugins/adoption-insights-backend minor v0.8.4
@red-hat-developer-hub/backstage-plugin-adoption-insights-common workspaces/adoption-insights/plugins/adoption-insights-common minor v0.8.4
@red-hat-developer-hub/backstage-plugin-adoption-insights workspaces/adoption-insights/plugins/adoption-insights minor v0.8.4
@red-hat-developer-hub/backstage-plugin-analytics-module-adoption-insights workspaces/adoption-insights/plugins/analytics-module-adoption-insights minor v0.8.4

@HusneShabbir HusneShabbir left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@Eswaraiahsapram, please fix the CI so that we can get this PR in

@Eswaraiahsapram
Eswaraiahsapram force-pushed the adoption-insights-bump-1.51.2 branch from 95605f8 to ac11717 Compare June 16, 2026 06:35
@codecov

codecov Bot commented Jun 16, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 56.59%. Comparing base (cc5ab93) to head (f481a02).
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3403   +/-   ##
=======================================
  Coverage   56.59%   56.59%           
=======================================
  Files        2372     2372           
  Lines       95021    95021           
  Branches    26600    26603    +3     
=======================================
  Hits        53777    53777           
  Misses      40953    40953           
  Partials      291      291           
Flag Coverage Δ *Carryforward flag
adoption-insights 84.54% <ø> (ø)
ai-integrations 69.26% <ø> (ø) Carriedforward from cc5ab93
app-defaults 69.79% <ø> (ø) Carriedforward from cc5ab93
augment 46.67% <ø> (ø) Carriedforward from cc5ab93
boost 75.27% <ø> (ø) Carriedforward from cc5ab93
bulk-import 72.59% <ø> (ø) Carriedforward from cc5ab93
cost-management 13.55% <ø> (ø) Carriedforward from cc5ab93
dcm 60.72% <ø> (ø) Carriedforward from cc5ab93
extensions 56.18% <ø> (ø) Carriedforward from cc5ab93
global-floating-action-button 71.18% <ø> (ø) Carriedforward from cc5ab93
global-header 62.19% <ø> (ø) Carriedforward from cc5ab93
homepage 47.58% <ø> (ø) Carriedforward from cc5ab93
install-dynamic-plugins 56.77% <ø> (ø) Carriedforward from cc5ab93
intelligent-assistant 69.50% <ø> (ø) Carriedforward from cc5ab93
konflux 91.98% <ø> (ø) Carriedforward from cc5ab93
lightspeed 69.02% <ø> (ø) Carriedforward from cc5ab93
mcp-integrations 83.40% <ø> (ø) Carriedforward from cc5ab93
orchestrator 57.01% <ø> (ø) Carriedforward from cc5ab93
quickstart 65.11% <ø> (ø) Carriedforward from cc5ab93
sandbox 79.56% <ø> (ø) Carriedforward from cc5ab93
scorecard 82.66% <ø> (ø) Carriedforward from cc5ab93
theme 83.85% <ø> (ø) Carriedforward from cc5ab93
translations 5.15% <ø> (ø) Carriedforward from cc5ab93
x2a 79.31% <ø> (ø) Carriedforward from cc5ab93

*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 cc5ab93...f481a02. 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.

@Eswaraiahsapram
Eswaraiahsapram force-pushed the adoption-insights-bump-1.51.2 branch from bb50abf to 988ad0e Compare June 16, 2026 11:54
@karthikjeeyar

Copy link
Copy Markdown
Member

@Eswaraiahsapram please resolve the conflicts

@fullsend-ai-review

fullsend-ai-review Bot commented Jun 22, 2026

Copy link
Copy Markdown

Review

Findings

High

  • [scope-mismatch] workspaces/adoption-insights/packages/app/src/modules/nav/Sidebar.tsx — The PR title is "chore(adoption-insights): version bump to v1.51.2", claiming a routine version bump. However, the actual changes go well beyond a version bump: (1) a full Sidebar.tsx refactor migrating from manual items prop to the navItems API with nav.take()/nav.rest(), (2) addition of SidebarSearchModal integration, (3) addition of searchPlugin and techdocsPlugin as new app features with a new @backstage/plugin-techdocs dependency, (4) accessibility improvements adding aria-label to all CircularProgress components, (5) ESLint config refactoring, (6) removal of the nav-item:adoption-insights extension from the public API surface. These are feature additions, API surface changes, and accessibility improvements — not a version bump chore.
    Remediation: Either split this PR into separate changes (version bump, sidebar migration, accessibility, new plugin integrations) each with appropriate commit type (feat/fix/chore), or retitle this PR to accurately reflect the scope. The removal of nav-item:adoption-insights from the API report is a breaking change that warrants explicit documentation.

Medium

  • [scope-creep] workspaces/adoption-insights/plugins/adoption-insights/report-alpha.api.md:133 — The nav-item:adoption-insights extension definition is removed from the public API surface (report-alpha.api.md). This is a breaking change for any consumers that override or reference this extension. Bundling a breaking API surface change inside a "chore: version bump" PR obscures it from downstream consumers who rely on API reports to track compatibility.
    Remediation: Document this as a breaking change. If the nav-item extension removal is intentional due to the navItems API migration, it should be called out in the PR description and potentially in a changeset with a major/minor bump depending on the project's versioning policy.

Low

  • [missing-authorization] — No linked GitHub issue. The PR body references a JIRA ticket (RHIDP-13789) that is not publicly accessible. Non-trivial changes (21 files, sidebar API migration, new plugin dependencies, accessibility improvements) should have a publicly reviewable authorization artifact so that reviewers can verify scope alignment.

  • [naming-conventions] workspaces/adoption-insights/eslint.frontend-shared.cjs:38 — The PR changes the exported function from a named function declaration to an anonymous arrow function. The codebase is split: some workspaces already use the arrow function pattern, while others use named function declarations. Consider standardizing all workspaces to one pattern.

  • [edge-case] workspaces/adoption-insights/packages/app/src/modules/nav/Sidebar.tsx:37 — The Sidebar uses nav.take('page:search'), nav.take('page:catalog'), nav.take('page:techdocs'), nav.take('page:adoption-insights'). If any of these extension IDs do not match the actual names registered by the corresponding plugins, the sidebar item will silently not render. The IDs follow standard Backstage convention and the corresponding plugins are added in App.tsx, so this is likely correct.

Info

  • [test-integrity] workspaces/adoption-insights/e2e-tests/insights.test.ts:189 — The timeout for the "Rest of the panels have no data" test is increased from 15s to 60s, and a new pre-wait for the page heading is added. These changes do not weaken any assertions — the same conditions are checked, with more generous timing. No test integrity concern.
Previous run

Review

Reason: stale-head

The review agent reviewed commit d195a492bba82b876dd9b7efc7b4324df7529e69 but the PR HEAD is now e377c2ff99580d50f9bd07bf3d2331ef0ebfdb93. This review was discarded to avoid approving unreviewed code.

@fullsend-ai-review

Copy link
Copy Markdown

/fs-review

@Eswaraiahsapram
Eswaraiahsapram force-pushed the adoption-insights-bump-1.51.2 branch from e377c2f to 355fa45 Compare June 22, 2026 07:10
@fullsend-ai-review

fullsend-ai-review Bot commented Jun 22, 2026

Copy link
Copy Markdown

🤖 Review · ❌ Terminated · Started 7:11 AM UTC · Ended 7:23 AM UTC
Commit: 2e647e2 · View workflow run →

@fullsend-ai-review fullsend-ai-review Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

See the review comment for full details.

routeRef: RouteRef_2<undefined>;
};
}>;
'page:adoption-insights': OverridableExtensionDefinition<{

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

[medium] scope-creep

The nav-item:adoption-insights extension definition is removed from the public API surface (report-alpha.api.md). This is a breaking change for any consumers that override or reference this extension. Bundling a breaking API surface change inside a 'chore: version bump' PR obscures it from downstream consumers who rely on API reports to track compatibility.

Suggested fix: Document this as a breaking change. If the nav-item extension removal is intentional due to the navItems API migration, it should be called out in the PR description and potentially in a changeset with a major/minor bump depending on the project's versioning policy.


/**
* Shared ESLint config for frontend packages in the adoption-insights workspace.
*/

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

[low] naming-conventions

The PR changes the exported function from a named function declaration to an anonymous arrow function. The codebase is split between patterns. Consider standardizing all workspaces to one pattern.

const nav = navItems.withComponent(item => (
<SidebarItem icon={() => item.icon} to={item.href} text={item.title} />
));

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

[low] edge-case

The Sidebar uses nav.take() with extension IDs like 'page:search', 'page:catalog', etc. If any ID does not match the actual extension name registered by the corresponding plugin, the sidebar item will silently not render. The IDs follow standard Backstage convention and the corresponding plugins are added in App.tsx.

Comment thread workspaces/adoption-insights/e2e-tests/insights.test.ts
@fullsend-ai-review

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 7:11 AM UTC · Completed 7:23 AM UTC
Commit: 2e647e2 · View workflow run →

@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

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!

@sonarqubecloud

Copy link
Copy Markdown

Quality Gate Failed Quality Gate failed

Failed conditions
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

💡 Need a hand with PR review? Try Gitar by Sonar!

@christoph-jerolimov

Copy link
Copy Markdown
Member

Closing this since the workspace got updated in #3893 to Backstage 1.52

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.

4 participants