Skip to content

Commit 5f98fa6

Browse files
jmagakGitHub Actionsnickboldt
authored
RHIDP-6000: Release notes for Red Hat Developer Hub 1.6.0 (#1133)
Co-authored-by: GitHub Actions <[email protected]> Co-authored-by: Nick Boldt <[email protected]>
1 parent e0ac5ae commit 5f98fa6

8 files changed

+342
-31
lines changed

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

Lines changed: 83 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,88 @@
44

55
This section lists breaking changes in {product} {product-version}.
66

7+
[id="removed-functionality-rhidp-6215"]
8+
== The Topology-specific permission `topology.view.read` is removed
9+
10+
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`, `kubernetes.resources.read` and `kubernetes.proxy` for the Topology plugin, as the Topology-specific permission `topology.view.read` is removed.
11+
12+
If you are using a CSV permission file, update the following lines:
13+
14+
.Old Topology permission definition
15+
[source,csv]
16+
----
17+
p, role:default/topology-viewer, topology.view.read, read, allow
18+
p, role:default/topology-viewer, kubernetes.proxy, use, allow
19+
----
20+
21+
.New Topology permission definition
22+
[source,csv]
23+
----
24+
p, role:default/topology-viewer, kubernetes.clusters.read, read, allow
25+
p, role:default/topology-viewer, kubernetes.resources.read, read, allow
26+
p, role:default/topology-viewer, kubernetes.proxy, use, allow
27+
----
28+
29+
30+
.Additional resources
31+
* link:https://issues.redhat.com/browse/RHIDP-6215[RHIDP-6215]
32+
33+
[id="removed-functionality-rhidp-7365"]
34+
== Migration to the core Auditor service
35+
36+
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.
37+
38+
39+
.Additional resources
40+
* link:https://issues.redhat.com/browse/RHIDP-7365[RHIDP-7365]
41+
42+
[id="removed-functionality-rhidp-7373"]
43+
== {product} introduces the Backstage Audit Log Service
44+
45+
{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.
46+
47+
The key changes introduced by this transition include the following:
48+
49+
* Audit logging is now delegated to Backstage plugins. Each plugin in Backstage is responsible for implementing and emitting its own audit events.
50+
51+
* 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.
52+
53+
* 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.
54+
55+
* 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.
56+
57+
58+
59+
60+
.Additional resources
61+
* link:https://issues.redhat.com/browse/RHIDP-7373[RHIDP-7373]
62+
63+
[id="removed-functionality-rhidp-7433"]
64+
== The Tekton-specific permission `tekton.view.read` is removed
65+
66+
Previously, the Tekton plugin used `tekton.view.read` permission to control access. Users were unable to configure Tekton 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 Tekton plugin. You can now use Kubernetes plugin permissions `kubernetes.clusters.read`, `kubernetes.resources.read` and `kubernetes.proxy` for the Tekton plugin, as the Tekton-specific permission `tekton.view.read` is removed.
67+
68+
If you are using a CSV permission file, update the following lines:
69+
70+
.Old Tekton permission definition
71+
[source,csv]
72+
----
73+
p, role:default/tekton-viewer, tekton.view.read, read, allow
74+
p, role:default/tekton-viewer, kubernetes.proxy, use, allow
75+
----
76+
77+
.New Tekton permission definition
78+
[source,csv]
79+
----
80+
p, role:default/tekton-viewer, kubernetes.clusters.read, read, allow
81+
p, role:default/tekton-viewer, kubernetes.resources.read, read, allow
82+
p, role:default/tekton-viewer, kubernetes.proxy, use, allow
83+
----
84+
85+
86+
87+
.Additional resources
88+
* link:https://issues.redhat.com/browse/RHIDP-7433[RHIDP-7433]
89+
790

8-
None.
991

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

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,16 @@
44

55
This section lists deprecated functionalities in {product} {product-version}.
66

7+
[id="deprecated-functionality-rhidp-6368"]
8+
== Deprecation of dynamic imports with `import(...)`
9+
10+
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.
11+
12+
13+
14+
15+
.Additional resources
16+
* link:https://issues.redhat.com/browse/RHIDP-6368[RHIDP-6368]
17+
718

8-
None.
919

modules/release-notes/ref-release-notes-developer-preview.adoc

Lines changed: 2 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -8,15 +8,9 @@ This section lists Developer Preview features in {product} {product-version}.
88
====
99
Developer Preview features are not supported by Red Hat in any way and are not functionally complete or production-ready. Do not use Developer Preview features for production or business-critical workloads. Developer Preview features provide early access to functionality in advance of possible inclusion in a Red Hat product offering. Customers can use these features to test functionality and provide feedback during the development process. Developer Preview features might not have any documentation, are subject to change or removal at any time, and have received limited testing. Red Hat might provide ways to submit feedback on Developer Preview features without an associated SLA.
1010
11-
For more information about the support scope of Red Hat Developer Preview features, see https://access.redhat.com/support/offerings/devpreview/[Developer Preview Support Scope].
11+
For more information about the support scope of Red Hat Developer Preview features, see link:https://access.redhat.com/support/offerings/devpreview/[Developer Preview Support Scope].
1212
====
1313

14-
[id="developer-preview-rhdhpai-510"]
15-
== {product-local}
1614

17-
{product-local} ({product-local-very-short}) is now available as a Developer Preview feature, providing a lightweight, self-contained version of {product-very-short} that allows developers and platform engineers to work on templates, try out plugins, validate software catalogs, and do other tasks without having to install {product-short} on a Kubernetes cluster.
15+
None.
1816

19-
For more information about installing {product-local-very-short}, see link:https://github.com/redhat-developer/rhdh-local[{product-local} on Github].
20-
21-
.Additional resources
22-
* For more information, see the blog post, link:https://developers.redhat.com/blog/2025/03/31/run-red-hat-developer-hub-locally-ease[Run Red Hat Developer Hub Locally with Ease]

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

Lines changed: 72 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,77 @@
44

55
This section lists issues fixed in {product} {product-version}.
66

7+
== Fixed issues in 1.6.0
8+
9+
[id="bug-fix-rhidp-5731"]
10+
=== Updated the air-gapped installation guide for non-OpenShift platforms
11+
12+
Previously, {product} documentation did not highlight the {product-short} installation using Helm Chart in fully and partially air-gapped environments on supported Kubernetes platforms.
13+
14+
With this update, the documentation provides instructions for mirroring required container images, updating Helm values, and installing the chart, without relying on internet access.
15+
16+
17+
.Additional resources
18+
* link:https://issues.redhat.com/browse/RHIDP-5731[RHIDP-5731]
19+
20+
21+
[id="bug-fix-rhidp-6010"]
22+
=== Line wrapping enabled for long menu heading labels
23+
24+
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.
25+
26+
27+
.Additional resources
28+
* link:https://issues.redhat.com/browse/RHIDP-6010[RHIDP-6010]
29+
30+
31+
[id="bug-fix-rhidp-6015"]
32+
=== Dynamic favicon configuration in `app-config.yaml` is not displayed on the login page
33+
34+
Before this update, the app-config configuration `app.branding.iconLogo` was not applied as the favicon in the browser.
35+
36+
This issue has been fixed, and the app-config configuration `app.branding.iconLogo` now correctly sets the favicon in the browser.
37+
38+
39+
.Additional resources
40+
* link:https://issues.redhat.com/browse/RHIDP-6015[RHIDP-6015]
41+
42+
43+
[id="bug-fix-rhidp-6042"]
44+
=== Floating Action Button (FAB) positioned in the &#39;Bottom-Left&#39; slot on {product-short}
45+
46+
Previously, the Floating Action Button (FAB) appeared over the navigation sidebar when the slot was set to &#39;bottom-left&#39;. This placement obstructed access to navigation elements, potentially hindering user interaction.
47+
48+
With this update, the FAB&#39;s position is adjusted to render adjacent to the navigation for the &#39;bottom-left&#39; slot position. As a result, users can access navigation options without obstruction.
49+
50+
51+
.Additional resources
52+
* link:https://issues.redhat.com/browse/RHIDP-6042[RHIDP-6042]
53+
54+
55+
[id="bug-fix-rhidp-6448"]
56+
=== Manually added resolutions override resolutions added by `--suppress-native-package`
57+
58+
Earlier, the `export-dynamic-plugin` command did not overwrite manually added resolutions, which could result in incorrect package dependencies in the exported dynamic plugin.
59+
60+
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.
61+
62+
63+
.Additional resources
64+
* link:https://issues.redhat.com/browse/RHIDP-6448[RHIDP-6448]
65+
66+
67+
[id="bug-fix-rhidp-6597"]
68+
=== Fixed unreachable links in the Operator installation information page on the OpenShift console
69+
70+
Previously, the {product-short} Operator details page in the OpenShift web console contained links to some pages that could not be reached outside of the {company-name} network.
71+
With this update, the links in the Operator installation information page have been fixed.
72+
73+
74+
75+
76+
.Additional resources
77+
* link:https://issues.redhat.com/browse/RHIDP-6597[RHIDP-6597]
78+
779

8-
None.
980

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

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,14 @@
44

55
This section lists known issues in {product} {product-version}.
66

7+
[id="known-issue-rhidp-7435"]
8+
== ArgoCD plugin permission and Quay plugin permission are not displayed in the RBAC front-end UI
9+
10+
Permissions associated only with front-end plugins do not appear in the UI because they require a backend plugin to expose the permission framework&#39;s well-known endpoint. As a workaround, you can apply these permissions by using a CSV file or directly calling the REST API of the RBAC backend plugin. Affected plugins include ArgoCD (`argocd.view.read`) and Quay (`quay.view.read`).
11+
12+
13+
.Additional resources
14+
* link:https://issues.redhat.com/browse/RHIDP-7435[RHIDP-7435]
15+
716

8-
None.
917

0 commit comments

Comments
 (0)