Version Packages (boost)

[rhdh-bot]

Releases

@red-hat-developer-hub/backstage-plugin-boost@0.4.0

Minor Changes

• 9cfc354: Add type-appropriate adoption actions for all AI asset types in the AdoptionCard entity extension.

• 766e4aa: Add extensible browse filters via NFS AiCatalogFilterBlueprint. Deployers can disable built-in filters and third-party plugins can add new filters to the AI Catalog sidebar via app-config.

  Breaking: The page extension ID changed from page:boost to page:boost/ai-catalog. Update any app.extensions references in app-config.yaml accordingly.

Patch Changes

• 69b063b: Revert icon imports from @mui/icons-material back to @remixicon/react to align with BUI's internal icon library. Remove unused @mui/icons-material and @mui/material dependencies.

@red-hat-developer-hub/backstage-plugin-boost-backend-module-ogx@0.2.0

Minor Changes

• 54345de: Rename all Llama Stack references to OGX across the boost workspace. The upstream project has been renamed from llamastack to ogx. This changes npm package names, module IDs, cache key prefixes, config paths, provider identifiers, and entity name prefixes. Consumers must update imports from @red-hat-developer-hub/backstage-plugin-boost-backend-module-llamastack to @red-hat-developer-hub/backstage-plugin-boost-backend-module-ogx and from @red-hat-developer-hub/backstage-plugin-llamastack-entity-provider to @red-hat-developer-hub/backstage-plugin-ogx-entity-provider.

Patch Changes

• Updated dependencies [46f6034]
• Updated dependencies [54345de]
  • @red-hat-developer-hub/backstage-plugin-boost-common@0.1.4

@red-hat-developer-hub/backstage-plugin-ogx-entity-provider@0.2.0

Minor Changes

• 54345de: Rename all Llama Stack references to OGX across the boost workspace. The upstream project has been renamed from llamastack to ogx. This changes npm package names, module IDs, cache key prefixes, config paths, provider identifiers, and entity name prefixes. Consumers must update imports from @red-hat-developer-hub/backstage-plugin-boost-backend-module-llamastack to @red-hat-developer-hub/backstage-plugin-boost-backend-module-ogx and from @red-hat-developer-hub/backstage-plugin-llamastack-entity-provider to @red-hat-developer-hub/backstage-plugin-ogx-entity-provider.

@red-hat-developer-hub/backstage-plugin-boost-backend@0.1.4

Patch Changes

• 46f6034: Upgrade boost.agent.list from BasicPermission to ResourcePermission for conditional RBAC filtering via authorizeConditional(). Add BoostAuthorizedRequest type for attaching permission conditions to list-endpoint requests.
• 54345de: Rename all Llama Stack references to OGX across the boost workspace. The upstream project has been renamed from llamastack to ogx. This changes npm package names, module IDs, cache key prefixes, config paths, provider identifiers, and entity name prefixes. Consumers must update imports from @red-hat-developer-hub/backstage-plugin-boost-backend-module-llamastack to @red-hat-developer-hub/backstage-plugin-boost-backend-module-ogx and from @red-hat-developer-hub/backstage-plugin-llamastack-entity-provider to @red-hat-developer-hub/backstage-plugin-ogx-entity-provider.
• Updated dependencies [46f6034]
• Updated dependencies [54345de]
  • @red-hat-developer-hub/backstage-plugin-boost-common@0.1.4

@red-hat-developer-hub/backstage-plugin-boost-common@0.1.4

Patch Changes

• 46f6034: Upgrade boost.agent.list from BasicPermission to ResourcePermission for conditional RBAC filtering via authorizeConditional(). Add BoostAuthorizedRequest type for attaching permission conditions to list-endpoint requests.
• 54345de: Rename all Llama Stack references to OGX across the boost workspace. The upstream project has been renamed from llamastack to ogx. This changes npm package names, module IDs, cache key prefixes, config paths, provider identifiers, and entity name prefixes. Consumers must update imports from @red-hat-developer-hub/backstage-plugin-boost-backend-module-llamastack to @red-hat-developer-hub/backstage-plugin-boost-backend-module-ogx and from @red-hat-developer-hub/backstage-plugin-llamastack-entity-provider to @red-hat-developer-hub/backstage-plugin-ogx-entity-provider.

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 8:29 AM UTC · Completed 8:33 AM UTC
Commit: f57257e · View workflow run →

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 58.12%. Comparing base (54345de) to head (9a473cf).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3744   +/-   ##
=======================================
  Coverage   58.12%   58.12%           
=======================================
  Files        2422     2422           
  Lines       96490    96490           
  Branches    26870    26870           
=======================================
  Hits        56081    56081           
  Misses      38956    38956           
  Partials     1453     1453           

Flag	Coverage Δ		*Carryforward flag
adoption-insights	84.55% <ø> (ø)		Carriedforward from 54345de
ai-integrations	69.76% <ø> (ø)		Carriedforward from 54345de
app-defaults	69.79% <ø> (ø)		Carriedforward from 54345de
augment	46.67% <ø> (ø)		Carriedforward from 54345de
boost	76.77% <ø> (ø)
bulk-import	72.56% <ø> (ø)		Carriedforward from 54345de
cost-management	13.55% <ø> (ø)		Carriedforward from 54345de
dcm	60.72% <ø> (ø)		Carriedforward from 54345de
extensions	56.59% <ø> (ø)		Carriedforward from 54345de
global-floating-action-button	71.18% <ø> (ø)		Carriedforward from 54345de
global-header	66.50% <ø> (ø)		Carriedforward from 54345de
homepage	47.59% <ø> (ø)		Carriedforward from 54345de
install-dynamic-plugins	59.95% <ø> (ø)		Carriedforward from 54345de
intelligent-assistant	74.61% <ø> (ø)		Carriedforward from 54345de
konflux	91.98% <ø> (ø)		Carriedforward from 54345de
lightspeed	69.02% <ø> (ø)		Carriedforward from 54345de
mcp-integrations	83.40% <ø> (ø)		Carriedforward from 54345de
orchestrator	66.87% <ø> (ø)		Carriedforward from 54345de
quickstart	63.74% <ø> (ø)		Carriedforward from 54345de
sandbox	79.56% <ø> (ø)		Carriedforward from 54345de
scorecard	85.98% <ø> (ø)		Carriedforward from 54345de
theme	88.77% <ø> (ø)		Carriedforward from 54345de
translations	5.12% <ø> (ø)		Carriedforward from 54345de
x2a	79.20% <ø> (ø)		Carriedforward from 54345de

*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 54345de...9a473cf. 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 — PR #3744: Version Packages (boost)

Verdict: ✅ Approve

Summary

This is a standard automated changesets release PR created by rhdh-bot. It consumes the replace-remixicon-with-mui-icons changeset and performs the corresponding version bump for @red-hat-developer-hub/backstage-plugin-boost.

Changes reviewed

File	Change
workspaces/boost/.changeset/replace-remixicon-with-mui-icons.md	Deleted — changeset consumed by version process
workspaces/boost/plugins/boost/CHANGELOG.md	Added 0.3.1 patch entry matching the changeset description
workspaces/boost/plugins/boost/package.json	Version bumped 0.3.0 → 0.3.1

Checks performed

• Correctness: Version bump is consistent — patch changeset produces a correct semver patch increment (0.3.0 → 0.3.1). Changelog entry accurately reflects the consumed changeset. ✅
• Security: No source code changes; no secrets, credentials, or sensitive data in the diff. ✅
• Intent & coherence: Automated release PR is appropriately scoped to a single workspace (boost) with no unrelated changes. ✅
• Style/conventions: Changelog format follows the existing pattern in the file. ✅
• Documentation: Changelog is being updated as part of this PR — no staleness. ✅
• Cross-repo contracts: Internal package version bump only; no API or schema changes. ✅

No findings.

[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-retro]

🤖 Finished Retro · ✅ Success · Started 6:45 PM UTC · Completed 7:00 PM UTC
Commit: 9a473cf · View workflow run →

[fullsend-ai-retro]

Retro: PR #3744 — Version Packages (boost)

Verdict: No new proposals. The workflow exposed a stale-review gap that is already well-covered by existing upstream issues.

Timeline

1. Jul 14 08:28 — rhdh-bot opened PR Version Packages (boost) #3744 ("Version Packages (boost)") with 1 changeset (replace-remixicon-with-mui-icons, version 0.3.0 → 0.3.1).
2. Jul 14 08:29–08:33 — Review agent ran (run 29318166158), reviewed commit 1aded56, approved, applied ready-for-merge label. Agent correctly identified this as "a standard automated changesets release PR."
3. Jul 14 – Aug 4 — The backstage/changesets-action force-pushed the branch 17 times as new changesets merged to main. The PR grew from 1 changeset (patch bump) to 5 changesets (minor bump to 0.4.0, including adoption actions, extensible browse filters, OGX rename, and RBAC permissions).
4. Zero re-reviews triggered. Despite synchronize being listed in fullsend.yaml's pull_request_target types, and the changesets bot using RHDH_BOT_TOKEN (a PAT, not GITHUB_TOKEN), none of the 15 intermediate force pushes triggered a fullsend workflow run. The changed files are all under workspaces/boost/**, which matches the paths filter. Root cause of the missing triggers is unclear — possibly a GitHub platform quirk with pull_request_target + paths + force-push branch rebuilds (the action does git reset --hard to the base SHA before committing).
5. Aug 4 18:44 — gabemontero approved (no comments) and merged 8 seconds later. The agent's stale approval from Jul 14 and ready-for-merge label were the only automated signals.

Assessment

Practical risk was low. The PR contained only version bumps, changelog entries, and consumed changeset files — no source code changes. The human reviewer's approval was appropriate for this class of change.

The stale-review pattern is systemic, not novel. The agent reviewed 1 changeset but the PR was merged with 5. The ready-for-merge label applied on Jul 14 persisted across all 17 force pushes. This pattern — stale automated approval persisting as a PR grows — is extensively tracked upstream.

Evidence supporting existing issues

• fullsend-ai-review bot does not revoke stale APPROVED reviews on subsequent commits fullsend-ai/fullsend#827 (stale APPROVED reviews not revoked on new commits): This PR is a clear example — the agent's approval on commit 1aded56 was stale by merge time (commit 9a473cf), and was never dismissed or re-evaluated.
• Remove ready-for-merge label on force-push to prevent stale review approval from gating merge fullsend-ai/fullsend#5417 (remove ready-for-merge label on force-push): The label applied on Jul 14 survived 17 force pushes and a scope expansion from patch to minor version bump.
• Review agent should dismiss prior approval when re-review finds medium+ severity issues after scope expansion fullsend-ai/fullsend#3273 (dismiss prior approval on scope expansion): The PR scope expanded from 1 changeset to 5, changing the version bump level from patch to minor, with no re-review.
• Update fullsend.yaml workflow SHA to restore review dispatch for bot-authored PRs #4166 (restore review dispatch for bot-authored PRs): While that issue covers a different mechanism (workflow SHA), the underlying problem is the same class — bot-authored PRs not receiving expected review dispatch.

Open question

Why did none of the 17 force pushes trigger pull_request_target synchronize events in the fullsend workflow? The changesets bot uses RHDH_BOT_TOKEN (a PAT), and changed files match the paths filter. The backstage/changesets-action's branch rebuild pattern (git reset --hard to base SHA, then commit on top) may interact poorly with GitHub's path evaluation for synchronize events. This deserves investigation but falls under the scope of the existing issues listed above.