Release notes for Red Hat Developer Hub 1.6.0

Author: GitHub Actions

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

@@ -4,6 +4,29 @@
 
 This section lists deprecated functionalities in {product} {product-version}.
 
+[id="deprecated-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 via RBAC UI. With this update, users can configure Kubernetes plugin permissions via RBAC UI that now governs the access to Topology plugin. You can now use Kubernetes plugin permissions `kubernetes.clusters.read` and `kubernetes.resources.read` for Topology plugin, as topology-specific permission `topology.view.read` is removed. 
+
+If you are using csv permission file, please 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]
+
 
-None.
 

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

@@ -2,8 +2,32 @@
 [id="fixed-issues"]
 = Fixed issues
 
-This section lists issues fixed in {product} {product-version}.
+This section lists issues fixed in {product} {product-version} that have a significant impact on users.
+
+== Fixed issues in 1.6.0
+
+[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.
+
+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.
+
+
+.Additional resources
+* link:https://issues.redhat.com/browse/RHIDP-6042[RHIDP-6042]
+
+
+[id="bug-fix-rhidp-6448"]
+=== Manually added resolutions override resolutions added by `--suppress-native-package`
+
+Previously, manually added resolutions were not overwritten by the package export-dynamic-plugin command. This could lead to 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.
+
+
+.Additional resources
+* link:https://issues.redhat.com/browse/RHIDP-6448[RHIDP-6448]
 
 
-None.
 

modules/release-notes/ref-release-notes-new-features.adoc

@@ -4,5 +4,18 @@
 
 This section highlights new features in {product} {product-version}.
 
-None.
+[id="feature-rhidp-6253"]
+== {product-short} community plugins updated to Backstage 1.36
+
+The {product-short} community plugins have been updated to Backstage version 1.36.
+
+[id="feature-rhidp-6269"]
+== Added a new RBAC conditional rule `IS_OWNER` to RBAC plugin
+
+{product} has introduced a new RBAC conditional rule `IS_OWNER` that allows administrators to grant limited access to the RBAC plugin. This enhancement allows administrators to assign ownership to roles and control their team's access. Therefore, users can assign ownership to roles, which can be used to conditionally filter roles, permission policies, and conditional policies. 
+
+This enhancement removes the resource type from the `policy.entity.create` permission, preventing conditional rules from being applied to the permission. You can update all permission policies that utilize the resource type `policy-entity` with the action `create` (for example `role:default/some_role, policy-entity, create, allow` to `role:default/some_role, policy.entity.create, create, allow`) to prevent degradation in the future.
+
+
+