Skip to content

Commit 684b3bb

Browse files
author
GitHub Actions
committed
Release notes for Red Hat Developer Hub 1.6.0
1 parent 4d86704 commit 684b3bb

File tree

5 files changed

+101
-100
lines changed

5 files changed

+101
-100
lines changed

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

Lines changed: 33 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -5,53 +5,53 @@
55
This section lists breaking changes in {product} {product-version}.
66

77
[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` and `kubernetes.resources.read` 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 line:
13-
14-
.Old topology permission definition
15-
[source,csv]
16-
----
17-
p, role:default/topology-viewer, topology.view.read, read, allow
18-
----
19-
20-
.New topology permission definition
21-
[source,csv]
22-
----
23-
p, role:default/topology-viewer, kubernetes.clusters.read, read, allow
24-
p, role:default/topology-viewer, kubernetes.resources.read, read, allow
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` and `kubernetes.resources.read` 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 line:
13+
14+
.Old topology permission definition
15+
[source,csv]
16+
----
17+
p, role:default/topology-viewer, topology.view.read, read, allow
18+
----
19+
20+
.New topology permission definition
21+
[source,csv]
22+
----
23+
p, role:default/topology-viewer, kubernetes.clusters.read, read, allow
24+
p, role:default/topology-viewer, kubernetes.resources.read, read, allow
2525
----
2626

2727

2828
.Additional resources
2929
* link:https://issues.redhat.com/browse/RHIDP-6215[RHIDP-6215]
3030

3131
[id="removed-functionality-rhidp-7365"]
32-
== Migration to the core Auditor service
33-
32+
== Migration to the core Auditor service
33+
3434
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.
3535

3636

3737
.Additional resources
3838
* link:https://issues.redhat.com/browse/RHIDP-7365[RHIDP-7365]
3939

4040
[id="removed-functionality-rhidp-7373"]
41-
== {product} introduces the Backstage Audit Log Service
42-
43-
{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.
44-
45-
The key changes introduced by this transition include the following:
46-
47-
* Audit logging is now delegated to Backstage plugins. Each plugin in Backstage is responsible for implementing and emitting its own audit events.
48-
49-
* 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.
50-
51-
* 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.
52-
53-
* 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.
54-
41+
== {product} introduces the Backstage Audit Log Service
42+
43+
{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.
44+
45+
The key changes introduced by this transition include the following:
46+
47+
* Audit logging is now delegated to Backstage plugins. Each plugin in Backstage is responsible for implementing and emitting its own audit events.
48+
49+
* 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.
50+
51+
* 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.
52+
53+
* 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.
54+
5555

5656

5757

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,10 +5,10 @@
55
This section lists deprecated functionalities in {product} {product-version}.
66

77
[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-
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+
1212

1313

1414

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

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -7,10 +7,10 @@ This section lists issues fixed in {product} {product-version} that have a signi
77
== Fixed issues in 1.6.0
88

99
[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-
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+
1414
With this update, the documentation provides instructions for mirroring required container images, updating Helm values, and installing the chart, without relying on internet access.
1515

1616

@@ -19,8 +19,8 @@ With this update, the documentation provides instructions for mirroring required
1919

2020

2121
[id="bug-fix-rhidp-6010"]
22-
=== Line wrapping enabled for long menu heading labels
23-
22+
=== Line wrapping enabled for long menu heading labels
23+
2424
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.
2525

2626

@@ -29,10 +29,10 @@ Previously, menu items with long text such as _Platform Engineer Services_ were
2929

3030

3131
[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-
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+
3636
This issue has been fixed, and the app-config configuration `app.branding.iconLogo` now correctly sets the favicon in the browser.
3737

3838

@@ -41,10 +41,10 @@ This issue has been fixed, and the app-config configuration `app.branding.iconLo
4141

4242

4343
[id="bug-fix-rhidp-6042"]
44-
=== Floating Action Button (FAB) positioned in the 'Bottom-Left' slot on {product-short}
45-
46-
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.
47-
44+
=== Floating Action Button (FAB) positioned in the 'Bottom-Left' slot on {product-short}
45+
46+
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.
47+
4848
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.
4949

5050

@@ -53,10 +53,10 @@ With this update, the FAB's position is adjusted to render adjacent to the n
5353

5454

5555
[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-
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+
6060
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.
6161

6262

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

Lines changed: 44 additions & 44 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
1-
:_content-type: REFERENCE
2-
[id="new-features"]
3-
= New features
4-
5-
This section highlights new features in {product} {product-version}.
6-
7-
[id="feature-rhidp-3597"]
1+
:_content-type: REFERENCE
2+
[id="new-features"]
3+
= New features
4+
5+
This section highlights new features in {product} {product-version}.
6+
7+
[id="feature-rhidp-3597"]
88
== OpenTelemetry metrics support added to the Keycloak backend plugin
99

1010
With this update, the Keycloak backend plugin supports OpenTelemetry metrics, which monitors fetch operations and diagnoses potential issues.
@@ -24,16 +24,16 @@ backend_keycloak_fetch_data_batch_failure_count_total{taskInstanceId="df040f
2424
```
2525

2626
You can export metrics using any OpenTelemetry-compatible backend, such as **Prometheus**.
27-
28-
29-
[id="enhancement-rhidp-5039"]
27+
28+
29+
[id="enhancement-rhidp-5039"]
3030
== Enhanced session duration control and refresh token cookie policy
3131

3232
With this update, the maximum age of the refresh token cookie has been reduced to 400 days to align with the modern web browser policies. Additionally, a new configurable field, `sessionDuration`, has been introduced in the supported authentication providers. This allows administrators to specify custom user session durations, enabling better control over session timeouts and enforced logouts.
3333

34-
For more information, see link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.5/html-single/authentication_in_red_hat_developer_hub/index#idm140459408106672[Authentication in {product}].
35-
36-
[id="enhancement-rhidp-5987"]
34+
For more information, see link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.5/html-single/authentication_in_red_hat_developer_hub/index#idm140459408106672[Authentication in {product}].
35+
36+
[id="enhancement-rhidp-5987"]
3737
== Updated Auditor Service
3838

3939
{product} {product-version} introduces an enhancement to the RBAC and Bulk Import plugins, enabling users to utilize Backstage's new Auditor service. The key features include: ​
@@ -51,9 +51,9 @@ The audit log is now backed by the `@backstage/backend-plugin-api` package.​
5151
The Bulk Import backend plugin emits audit events for various operations, with the events are grouped logically by `eventId`.​
5252

5353

54-
55-
56-
[id="feature-rhidp-6158"]
54+
55+
56+
[id="feature-rhidp-6158"]
5757
== Renamed `Create` to `Self-service`
5858

5959
The term `Create` has been renamed to `Self-service` across key UI areas to better align with the self-service functionality provided through the Backstage scaffolder, enhancing clarity for users.
@@ -63,16 +63,16 @@ This change applies to the following areas:
6363
* Sidebar navigation
6464
* Global header
6565
* Catalog page
66-
* Scaffolder page
67-
68-
[id="enhancement-rhidp-6173"]
66+
* Scaffolder page
67+
68+
[id="enhancement-rhidp-6173"]
6969
== Simplify Operator-backed deployments on OpenShift with automatic `baseUrl` configuration
7070

7171
Previously, deploying {product-short} using the Operator required manually configuring the `baseUrl` settings in the custom app-config ConfigMap.
7272

73-
With this update, the Operator can now automatically compute the default application URL based on the OpenShift cluster ingress domain and the custom Route settings in the `Backstage` Custom Resource. It will then populate this as the default `baseUrl` in the app-config ConfigMap that it generates for the {product-short} instance. This functionality is specific to OpenShift. The Operator fills the following fields in the default app-config ConfigMap: `app.baseUrl`, `backend.baseUrl`, and `backend.cors.origin`. As a result, this eliminates the need to manually set such values for most Operator-backed deployments on OpenShift, though you can still override these settings in your custom app-config ConfigMap.
74-
75-
[id="enhancement-rhidp-6184"]
73+
With this update, the Operator can now automatically compute the default application URL based on the OpenShift cluster ingress domain and the custom Route settings in the `Backstage` Custom Resource. It will then populate this as the default `baseUrl` in the app-config ConfigMap that it generates for the {product-short} instance. This functionality is specific to OpenShift. The Operator fills the following fields in the default app-config ConfigMap: `app.baseUrl`, `backend.baseUrl`, and `backend.cors.origin`. As a result, this eliminates the need to manually set such values for most Operator-backed deployments on OpenShift, though you can still override these settings in your custom app-config ConfigMap.
74+
75+
[id="enhancement-rhidp-6184"]
7676
== New sidebar item visibility configuration
7777

7878
{product} now supports a clean and flexible way to hide sidebar items using a new enabled key in the sidebar menu configuration. If set to false, the specified sidebar item will no longer appear in the UI, while maintaining full backward compatibility with existing configurations.
@@ -116,44 +116,44 @@ app:
116116
logo: false # hides sidebar logo
117117
settings: false # hides settings item
118118
administration: false # hides administration item
119-
----
120-
121-
[id="feature-rhidp-6253"]
119+
----
120+
121+
[id="feature-rhidp-6253"]
122122
== {product-short} community plugins updated to Backstage 1.36
123123

124-
The {product-short} community plugins have been updated to Backstage version 1.36.
125-
126-
[id="feature-rhidp-6269"]
124+
The {product-short} community plugins have been updated to Backstage version 1.36.
125+
126+
[id="feature-rhidp-6269"]
127127
== Added a new RBAC conditional rule `IS_OWNER` to RBAC plugin
128128

129129
{product} introduces a new RBAC conditional rule, `IS_OWNER`, that allows administrators to assign ownership to roles and control access to the RBAC plugin. This enhancement enables more granular access control by allowing ownership-based filtering of roles, permission policies, and conditional policies.
130130

131131
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.
132-
133-
134-
[id="feature-rhidp-6555"]
132+
133+
134+
[id="feature-rhidp-6555"]
135135
== Support for high availability in {aks-brand-name}
136136

137137
{product} now supports high availability setups in {aks-brand-name} ({aks-short}). This enhancement allows the deployment to scale beyond a single replica, ensuring the application remains operational and accessible even in the event of failures or disruptions.
138138

139-
For more information, see link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.5/html-single/configuring_red_hat_developer_hub/index#HighAvailability[_Configuring high availability in Red Hat Developer Hub_].
140-
141-
[id="feature-rhidp-6764"]
139+
For more information, see link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.5/html-single/configuring_red_hat_developer_hub/index#HighAvailability[_Configuring high availability in Red Hat Developer Hub_].
140+
141+
[id="feature-rhidp-6764"]
142142
== Added `@backstage/plugin-scaffolder-backend-module-github` plugin for {product-short}
143143

144-
{product} now supports the `@backstage/plugin-scaffolder-backend-module-github` plugin, enabling GitHub Actions within software templates. With this integration, you can securely create and manage repositories, open pull requests, trigger GitHub Actions workflows, and more, all directly from the software template. This plugin empowers users to automate GitHub interactions and workflows with ease.
145-
146-
[id="enhancement-rhidp-6882"]
144+
{product} now supports the `@backstage/plugin-scaffolder-backend-module-github` plugin, enabling GitHub Actions within software templates. With this integration, you can securely create and manage repositories, open pull requests, trigger GitHub Actions workflows, and more, all directly from the software template. This plugin empowers users to automate GitHub interactions and workflows with ease.
145+
146+
[id="enhancement-rhidp-6882"]
147147
== Default OIDC sign-in resolver updated
148148

149-
With this update, the default resolver for OIDC sign-in is set to `oidcSubClaimMatchingKeycloakUserId` to enhance security. This resolver is now also available as a configurable option under the sign-in resolver settings.
150-
151-
[id="feature-rhidp-7424"]
149+
With this update, the default resolver for OIDC sign-in is set to `oidcSubClaimMatchingKeycloakUserId` to enhance security. This resolver is now also available as a configurable option under the sign-in resolver settings.
150+
151+
[id="feature-rhidp-7424"]
152152
== New dynamic plugin for Kubernetes scaffolder actions
153153

154154
With this update, {product-short} introduces the @backstage-community/plugin-scaffolder-backend-module-kubernetes plugin as a dynamic plugin, enabling Backstage template actions for Kubernetes. Currently, it includes the create-namespace action. This dynamic plugin is disabled by default.
155155

156-
For more information, see link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.5/html-single/dynamic_plugins_reference/index#red-hat-supported-plugins[{company-name} supported plugins].
157-
158-
159-
156+
For more information, see link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.5/html-single/dynamic_plugins_reference/index#red-hat-supported-plugins[{company-name} supported plugins].
157+
158+
159+

‎modules/release-notes/ref-release-notes-technology-preview.adoc‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,4 +13,5 @@ See: link:https://access.redhat.com/support/offerings/techpreview/[Technology Pr
1313
====
1414

1515

16-
None.
16+
None.
17+

0 commit comments

Comments
 (0)