Release notes for Red Hat Developer Hub 1.6.0

Author: GitHub Actions

modules/release-notes/ref-release-notes-breaking-changes.adoc

@@ -5,53 +5,53 @@
 This section lists breaking changes in {product} {product-version}.
 
 [id="removed-functionality-rhidp-6215"]
-== The Topology-specific permission `topology.view.read` is removed
-
-Previously, the Topology plugin used `topology.view.read` permission to control access. Users were unable to configure Topology permissions using the RBAC UI. With this update, users can configure Kubernetes plugin permissions using the RBAC UI, which now governs the access to the Topology plugin. You can now use Kubernetes plugin permissions `kubernetes.clusters.read` and `kubernetes.resources.read` for the Topology plugin, as the topology-specific permission `topology.view.read` is removed. 
-
-If you are using a CSV permission file, update the following line:
-
-.Old topology permission definition
-[source,csv]
-----
-p, role:default/topology-viewer, topology.view.read, read, allow
-----
-
-.New topology permission definition
-[source,csv]
-----
-p, role:default/topology-viewer, kubernetes.clusters.read, read, allow
-p, role:default/topology-viewer, kubernetes.resources.read, read, allow
+== The Topology-specific permission `topology.view.read` is removed
+
+Previously, the Topology plugin used `topology.view.read` permission to control access. Users were unable to configure Topology permissions using the RBAC UI. With this update, users can configure Kubernetes plugin permissions using the RBAC UI, which now governs the access to the Topology plugin. You can now use Kubernetes plugin permissions `kubernetes.clusters.read` and `kubernetes.resources.read` for the Topology plugin, as the topology-specific permission `topology.view.read` is removed. 
+
+If you are using a CSV permission file, update the following line:
+
+.Old topology permission definition
+[source,csv]
+----
+p, role:default/topology-viewer, topology.view.read, read, allow
+----
+
+.New topology permission definition
+[source,csv]
+----
+p, role:default/topology-viewer, kubernetes.clusters.read, read, allow
+p, role:default/topology-viewer, kubernetes.resources.read, read, allow
 ----
 
 
 .Additional resources
 * link:https://issues.redhat.com/browse/RHIDP-6215[RHIDP-6215]
 
 [id="removed-functionality-rhidp-7365"]
-== Migration to the core Auditor service
-
+== Migration to the core Auditor service
+
 The Auditor format, including audit fields and event names, and IDs, has been updated to align with the new Auditor service conventions defined by the upstream Backstage Auditor Service. Filtering queries based on the old format may fail to work as expected.
 
 
 .Additional resources
 * link:https://issues.redhat.com/browse/RHIDP-7365[RHIDP-7365]
 
 [id="removed-functionality-rhidp-7373"]
-== {product} introduces the Backstage Audit Log Service
-
-{product} {product-version} introduces the Backstage Audit Log Service, which replaces the custom audit logging system. This is a significant structural and behavioral change to how audit events are generated and consumed.
-
-The key changes introduced by this transition include the following:
-
-* Audit logging is now delegated to Backstage plugins. Each plugin in Backstage is responsible for implementing and emitting its own audit events.
-
-* Audit event names, structure, and content may differ per plugin. Audit events are scoped and designed independently within each plugin using the standardized upstream mechanism, which automatically captures actor details and plugin context.
-
-* New Event Structure and Naming: Audit event names now follow Backstage’s conventions (for example, lowercase, kebab-case names), and include structured metadata such as `actionType`. Legacy {product-short} event names (for example, `ScaffolderTaskCreation`, `CatalogEntityDeletion`) are no longer used.
-
-* Enhanced Log Context: Each audit event includes the plugin context, making it easier to filter logs for specific functional areas. You can filter by the event IDs or metadata associated with that plugin. 
-
+== {product} introduces the Backstage Audit Log Service
+
+{product} {product-version} introduces the Backstage Audit Log Service, which replaces the custom audit logging system. This is a significant structural and behavioral change to how audit events are generated and consumed.
+
+The key changes introduced by this transition include the following:
+
+* Audit logging is now delegated to Backstage plugins. Each plugin in Backstage is responsible for implementing and emitting its own audit events.
+
+* Audit event names, structure, and content may differ per plugin. Audit events are scoped and designed independently within each plugin using the standardized upstream mechanism, which automatically captures actor details and plugin context.
+
+* New Event Structure and Naming: Audit event names now follow Backstage’s conventions (for example, lowercase, kebab-case names), and include structured metadata such as `actionType`. Legacy {product-short} event names (for example, `ScaffolderTaskCreation`, `CatalogEntityDeletion`) are no longer used.
+
+* Enhanced Log Context: Each audit event includes the plugin context, making it easier to filter logs for specific functional areas. You can filter by the event IDs or metadata associated with that plugin. 
+
 
 
 

modules/release-notes/ref-release-notes-deprecated-functionalities.adoc

@@ -5,10 +5,10 @@
 This section lists deprecated functionalities in {product} {product-version}.
 
 [id="deprecated-functionality-rhidp-6368"]
-== Deprecation of dynamic imports with `import(...)`
-
-The use of dynamic imports with `import(...)` has been deprecated and is no longer supported. The Backstage CLI supports native ESM in Node.js code, giving access to the importing of ESM-only packages. Therefore, you must now use `require(...)` as typeof `import(...)` when working with ESM or CommonJS packages.
-
+== Deprecation of dynamic imports with `import(...)`
+
+The use of dynamic imports with `import(...)` has been deprecated and is no longer supported. The Backstage CLI supports native ESM in Node.js code, giving access to the importing of ESM-only packages. Therefore, you must now use `require(...)` as typeof `import(...)` when working with ESM or CommonJS packages.
+
 
 
 

modules/release-notes/ref-release-notes-fixed-issues.adoc

@@ -7,10 +7,10 @@ This section lists issues fixed in {product} {product-version} that have a signi
 == Fixed issues in 1.6.0
 
 [id="bug-fix-rhidp-5731"]
-=== Updated the air-gapped installation guide for non-OpenShift platforms
-
-Previously, {product} documentation did not highlight the {product-short} installation using Helm Chart in fully and partially air-gapped environments on supported Kubernetes platforms.
-
+=== Updated the air-gapped installation guide for non-OpenShift platforms
+
+Previously, {product} documentation did not highlight the {product-short} installation using Helm Chart in fully and partially air-gapped environments on supported Kubernetes platforms.
+
 With this update, the documentation provides instructions for mirroring required container images, updating Helm values, and installing the chart, without relying on internet access.
 
 
@@ -19,8 +19,8 @@ With this update, the documentation provides instructions for mirroring required
 
 
 [id="bug-fix-rhidp-6010"]
-=== Line wrapping enabled for long menu heading labels
-
+=== Line wrapping enabled for long menu heading labels
+
 Previously, menu items with long text such as _Platform Engineer Services_ were cut off in the sidebar menu. With this update, line wrapping has been enabled for long menu heading labels, preventing the trimming and ensuring full text visibility.
 
 
@@ -29,10 +29,10 @@ Previously, menu items with long text such as _Platform Engineer Services_ were
 
 
 [id="bug-fix-rhidp-6015"]
-=== Dynamic favicon configuration in `app-config.yaml` is not displayed on the login page
-
-Before this update, the app-config configuration `app.branding.iconLogo` was not applied as the favicon in the browser.
-
+=== Dynamic favicon configuration in `app-config.yaml` is not displayed on the login page
+
+Before this update, the app-config configuration `app.branding.iconLogo` was not applied as the favicon in the browser.
+
 This issue has been fixed, and the app-config configuration `app.branding.iconLogo` now correctly sets the favicon in the browser.
 
 
@@ -41,10 +41,10 @@ This issue has been fixed, and the app-config configuration `app.branding.iconLo
 
 
 [id="bug-fix-rhidp-6042"]
-=== Floating Action Button (FAB) positioned in the 'Bottom-Left' slot on {product-short}
-
-Previously, the Floating Action Button (FAB) appeared over the navigation sidebar when the slot was set to 'bottom-left'. This placement obstructed access to navigation elements, potentially hindering user interaction.
-
+=== Floating Action Button (FAB) positioned in the 'Bottom-Left' slot on {product-short}
+
+Previously, the Floating Action Button (FAB) appeared over the navigation sidebar when the slot was set to 'bottom-left'. This placement obstructed access to navigation elements, potentially hindering user interaction.
+
 With this update, the FAB's position is adjusted to render adjacent to the navigation for the 'bottom-left' slot position. As a result, users can access navigation options without obstruction.
 
 
@@ -53,10 +53,10 @@ With this update, the FAB's position is adjusted to render adjacent to the n
 
 
 [id="bug-fix-rhidp-6448"]
-=== Manually added resolutions override resolutions added by `--suppress-native-package`
-
-Earlier, the `export-dynamic-plugin` command did not overwrite manually added resolutions, which could result in incorrect package dependencies in the exported dynamic plugin.
-
+=== Manually added resolutions override resolutions added by `--suppress-native-package`
+
+Earlier, the `export-dynamic-plugin` command did not overwrite manually added resolutions, which could result in incorrect package dependencies in the exported dynamic plugin.
+
 With this update, the `package export-dynamic-plugin` overwrites manually added resolutions, ensuring backstage dependencies are hoisted and native dependencies are suppressed from the exported dynamic plugin.