Open
Conversation
github-actions
bot
force-pushed
the
changesets-release/scorecard/main
branch
from
fa0b7a0 to
828f49b
Compare
rhdh-bot
requested review from
a team,
Eswaraiahsapram,
christoph-jerolimov and
its-mitesh-kumar
as code owners
github-actions
bot
force-pushed
the
changesets-release/scorecard/main
branch
6 times, most recently
from
a0afb31 to
6394b1a
Compare
github-actions
bot
force-pushed
the
changesets-release/scorecard/main
branch
2 times, most recently
from
a922168 to
2d55a92
Compare
github-actions
bot
force-pushed
the
changesets-release/scorecard/main
branch
6 times, most recently
from
efe9f0a to
aa19ebf
Compare
github-actions
bot
force-pushed
the
changesets-release/scorecard/main
branch
3 times, most recently
from
649d4f2 to
71d1b23
Compare
Member
|
Let's merge after #2640 goes in |
github-actions
bot
force-pushed
the
changesets-release/scorecard/main
branch
from
71d1b23 to
09ec7e3
Compare
4 tasks
Member
|
Waiting also on #2609 |
github-actions
bot
force-pushed
the
changesets-release/scorecard/main
branch
from
09ec7e3 to
a08b471
Compare
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Releases
@red-hat-developer-hub/backstage-plugin-scorecard@2.5.0
Minor Changes
55226c2: Introduces custom threshold rule icons that can be configured in
app-config.yaml.f13f583: Adding scorecardHomepage and metric page extension, also added e2e support in nfs
0d64361: Adds a Scorecard Entities page that allows users to drill down from aggregated scorecard KPIs to view the individual entities contributing to the overall score. The page displays entity-level metric values and status, enabling users to identify services impacting the metric and investigate issues more effectively.
243ad0a: Aggregated scorecards now use aggregation IDs and dedicated HTTP routes. The old catalog-aggregations URL still works but is deprecated (not removed).
Backend (
@red-hat-developer-hub/backstage-plugin-scorecard-backend)GET /metrics/:metricId/catalog/aggregations— responses are unchanged, but the handler emits RFC 8594DeprecationandLinkheaders (alternate successor:GET .../aggregations/:aggregationId) and logs a warning. PreferGET /aggregations/:aggregationIdfor new integrations.GET /aggregations/:aggregationIdfor aggregated results using configured aggregation.GET /aggregations/:aggregationId/metadatafor KPI titles, descriptions, and aggregation metadata consumed by the UI.Common (
@red-hat-developer-hub/backstage-plugin-scorecard-common)Frontend (
@red-hat-developer-hub/backstage-plugin-scorecard)aggregationId, fetch metadata from the new endpoint, and keep localized threshold and error strings where translation keys exist.Action for adopters: Configure aggregated scorecards with
aggregationIdvalues that match backend aggregation config, replace direct calls toGET /metrics/:metricId/catalog/aggregationswithGET /aggregations/:aggregationId(and metadata if you need the same labels as the plugin UI).99aa8ff: Added support for the New Frontend System (NFS), including an alpha export for NFS apps and a new
app-nextpackage.Patch Changes
@red-hat-developer-hub/backstage-plugin-scorecard-backend@2.5.0
Minor Changes
55226c2: Introduces custom threshold rule icons that can be configured in
app-config.yaml.bd5f3e8: added disable metric feature to the pull metric task
243ad0a: Aggregated scorecards now use aggregation IDs and dedicated HTTP routes. The old catalog-aggregations URL still works but is deprecated (not removed).
Backend (
@red-hat-developer-hub/backstage-plugin-scorecard-backend)GET /metrics/:metricId/catalog/aggregations— responses are unchanged, but the handler emits RFC 8594DeprecationandLinkheaders (alternate successor:GET .../aggregations/:aggregationId) and logs a warning. PreferGET /aggregations/:aggregationIdfor new integrations.GET /aggregations/:aggregationIdfor aggregated results using configured aggregation.GET /aggregations/:aggregationId/metadatafor KPI titles, descriptions, and aggregation metadata consumed by the UI.Common (
@red-hat-developer-hub/backstage-plugin-scorecard-common)Frontend (
@red-hat-developer-hub/backstage-plugin-scorecard)aggregationId, fetch metadata from the new endpoint, and keep localized threshold and error strings where translation keys exist.Action for adopters: Configure aggregated scorecards with
aggregationIdvalues that match backend aggregation config, replace direct calls toGET /metrics/:metricId/catalog/aggregationswithGET /aggregations/:aggregationId(and metadata if you need the same labels as the plugin UI).c83b206: Adds the ability to drill down from aggregated scorecard KPIs to view the individual entities that contribute to the overall score. This enables managers and platform engineers to identify specific services impacting metrics and troubleshoot issues at the entity level.
Patch Changes
@red-hat-developer-hub/backstage-plugin-scorecard-backend-module-dependabot@0.2.0
Minor Changes
Patch Changes
@red-hat-developer-hub/backstage-plugin-scorecard-common@2.5.0
Minor Changes
55226c2: Introduces custom threshold rule icons that can be configured in
app-config.yaml.243ad0a: Aggregated scorecards now use aggregation IDs and dedicated HTTP routes. The old catalog-aggregations URL still works but is deprecated (not removed).
Backend (
@red-hat-developer-hub/backstage-plugin-scorecard-backend)GET /metrics/:metricId/catalog/aggregations— responses are unchanged, but the handler emits RFC 8594DeprecationandLinkheaders (alternate successor:GET .../aggregations/:aggregationId) and logs a warning. PreferGET /aggregations/:aggregationIdfor new integrations.GET /aggregations/:aggregationIdfor aggregated results using configured aggregation.GET /aggregations/:aggregationId/metadatafor KPI titles, descriptions, and aggregation metadata consumed by the UI.Common (
@red-hat-developer-hub/backstage-plugin-scorecard-common)Frontend (
@red-hat-developer-hub/backstage-plugin-scorecard)aggregationId, fetch metadata from the new endpoint, and keep localized threshold and error strings where translation keys exist.Action for adopters: Configure aggregated scorecards with
aggregationIdvalues that match backend aggregation config, replace direct calls toGET /metrics/:metricId/catalog/aggregationswithGET /aggregations/:aggregationId(and metadata if you need the same labels as the plugin UI).c83b206: Adds the ability to drill down from aggregated scorecard KPIs to view the individual entities that contribute to the overall score. This enables managers and platform engineers to identify specific services impacting metrics and troubleshoot issues at the entity level.
@red-hat-developer-hub/backstage-plugin-scorecard-node@2.5.0
Minor Changes
app-config.yaml.Patch Changes
@red-hat-developer-hub/backstage-plugin-scorecard-backend-module-github@2.5.0
Patch Changes
@red-hat-developer-hub/backstage-plugin-scorecard-backend-module-jira@2.5.0
Patch Changes
@red-hat-developer-hub/backstage-plugin-scorecard-backend-module-openssf@0.1.7
Patch Changes