You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/release-notes/ref-release-notes-fixed-issues.adoc
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ This section lists issues fixed in {product} {product-version}.
9
9
[id="bug-fix-rhdhbugs-1878"]
10
10
=== Fixed incorrect version detection for local plugin updates
11
11
12
-
Before this update, local plugins within the image were incorrectly detected for updates due to version misidentification. This led to users being unable to update local plugins from wrappers, resulting in outdated functionality. With this release, local plugin updates are now automatically detected, eliminating the need for manual adjustments and ensuring seamless plugin version updates for end users.
12
+
Before this update, local plugins within the image were incorrectly detected for updates due to version misidentification. This led to users being unable to update local plugins from wrappers, resulting in outdated functionality. With this release, local plugin updates are automatically detected, eliminating the need for manual adjustments and ensuring seamless plugin version updates for end users.
13
13
14
14
15
15
.Additional resources
@@ -19,15 +19,15 @@ Before this update, local plugins within the image were incorrectly detected for
Before this update, the header column on the documentation page lacked translations, causing wrong header labels for end users. This issue led to end users seeing `table.header.actions` on the documentation page. With this release, the header column correctly translates to `Actions`, ensuring end users now see the correct label on the documentation page.
22
+
Before this update, the header column on the documentation page lacked translations, causing wrong header labels for end users. This issue led to end users seeing `table.header.actions` on the documentation page. With this release, the header column correctly translates to `Actions`, making sure the end users see the correct label on the documentation page.
=== Fixed database service name error to ensure {product-very-short} instance starts correctly
30
+
=== Fixed database service name error to make sure {product-very-short} instance starts correctly
31
31
32
32
Before this update, deploying Helm-based Orchestrator with local Database in replication mode failed due to a wrong database service name. This caused the {product-very-short} instance to fail to start. With this release, the {product-very-short} instance starts correctly, allowing the correct setting of the database service name in the {product-very-short} instance configuration.
33
33
@@ -39,7 +39,7 @@ Before this update, deploying Helm-based Orchestrator with local Database in rep
39
39
[id="bug-fix-rhdhbugs-2041"]
40
40
=== Orchestrator plugin updated to 1.7.1
41
41
42
-
Before this update, the latest Orchestrator feature set was unavailable because the release included the outdated Orchestrator plugin version `1.6`. This issue is resolved in {product-very-short} `1.7.1`. The Orchestrator plugin is now updated to version `1.7.1`, ensuring that users have access to the latest features and functionality.
42
+
Before this update, the latest Orchestrator feature set was unavailable because the release included the outdated Orchestrator plugin version `1.6`. This issue is resolved in {product-very-short} `1.7.1`. The Orchestrator plugin is updated to version `1.7.1`, making sure that users have access to the latest features and functionality.
43
43
44
44
45
45
.Additional resources
@@ -124,7 +124,7 @@ With this update, after each refresh, the cards correctly display the custom tit
124
124
125
125
126
126
[id="bug-fix-rhdhbugs-834"]
127
-
=== Fixed role name updates via API to correctly propagate to permissions, metadata, and conditions
127
+
=== Fixed role name updates through API to correctly propagate to permissions, metadata, and conditions
128
128
129
129
Previously, when a role name was updated using the RBAC API, existing permissions, conditions, and metadata were not updated and remained mapped to the old role name.
130
130
With this update, role name changes are now correctly updated.
@@ -137,7 +137,7 @@ With this update, role name changes are now correctly updated.
137
137
[id="bug-fix-rhdhbugs-903"]
138
138
=== Fixed role actions tooltip delay issue
139
139
140
-
Previously, tooltips on action icons in the Role list table of the Role-Based Access Control (RBAC) page were slow to appear on hover.
140
+
Previously, tooltips on action icons in the *Role list* table of the Role-Based Access Control (RBAC) page were slow to appear on hover.
141
141
142
142
This issue has been fixed, ensuring that tooltips now appear immediately when hovering over action icons in the RBAC page.
143
143
@@ -163,7 +163,7 @@ With this update, the UI shows an empty state with a message to enable the backe
163
163
164
164
Previously, the *Profile dropdown* in the Global Header showed `Guest` instead of the logged-in user’s display name when logging in using the OIDC authentication.
165
165
166
-
With this update, the *Profile dropdown* now correctly displays the user's name by first checking `spec.profile.displayName`, then `metadata.title`, and finally falls back to the name shown on the *Profile card* in the *Settings* page if neither is available.
166
+
With this release, the *Profile dropdown* correctly displays the user's name by first checking `spec.profile.displayName`, then `metadata.title`, and finally falls back to the name shown on the *Profile card* in the *Settings* page if neither is available.
This section highlights new features in {product}{product-version}.
6
-
7
-
[id="enhancement-rhdhbugs-1885"]
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="enhancement-rhdhbugs-1885"]
8
8
== Improved plugin configuration merging for include files
9
9
10
10
Previously, include plugin configuration files would overwrite existing files. With this update, {product} will merge configurations from existing include files, only overwriting specific keys while preserving keys defined in existing include files, mirroring the behavior for the `plugins` key.
11
-
12
-
13
-
[id="feature-rhdhbugs-1979"]
11
+
12
+
13
+
[id="feature-rhdhbugs-1979"]
14
14
== Orchestrator 1.7 available
15
15
16
16
As of {product-very-short} 1.7.1, the Orchestrator plugin 1.7.1 is now available.
@@ -20,30 +20,30 @@ As of {product-very-short} 1.7.1, the Orchestrator plugin 1.7.1 is now available
20
20
21
21
22
22
23
-
24
-
25
-
[id="enhancement-rhdhbugs-1981"]
23
+
24
+
25
+
[id="enhancement-rhdhbugs-1981"]
26
26
== Full support for Adoption Insights plugins
27
27
28
-
With this update, {company-name} fully supports the Adoption Insights plugins. These plugins are no longer Technology Preview.
29
-
30
-
[id="feature-rhidp-6628"]
28
+
With this update, {company-name} fully supports the Adoption Insights plugins. These plugins are no longer Technology Preview.
29
+
30
+
[id="feature-rhidp-6628"]
31
31
== Dynamic plugin dependency management
32
32
{product} 1.7 adds dynamic plugin dependency management, so that the Operator can manage Kubernetes resources required by plugins.
33
33
34
-
For more information, see link:https://github.com/redhat-developer/rhdh-operator/blob/main/docs/dynamic-plugins.md#dynamic-plugins-dependency-management[Dynamic plugin dependency management]
35
-
36
-
[id="feature-rhidp-6633"]
34
+
For more information, see link:https://github.com/redhat-developer/rhdh-operator/blob/main/docs/dynamic-plugins.md#dynamic-plugins-dependency-management[Dynamic plugin dependency management]
35
+
36
+
[id="feature-rhidp-6633"]
37
37
== Added Orchestrator plugins with dependencies to {product-very-short} profile.
38
38
39
-
With this update, Orchestrator plugins with dependencies are added to the {product-very-short} profile. The Orchestrator plugin is disabled by default. When you enable the Orchestrator plugin, it will deploy dependencies and work out of the box on {product-very-short}.
40
-
41
-
[id="enhancement-rhidp-6657"]
39
+
With this update, Orchestrator plugins with dependencies are added to the {product-very-short} profile. The Orchestrator plugin is disabled by default. When you enable the Orchestrator plugin, it will deploy dependencies and work out of the box on {product-very-short}.
40
+
41
+
[id="enhancement-rhidp-6657"]
42
42
== Updated {product-very-short} theme
43
43
44
-
With this update, the `@redhat-developer/red-hat-developer-hub-theme` package is replaced with the plugin version from the `rhdh-plugins` repository to improve theme integration and visual consistency. Minor UI enhancements include updated border radius on cards.
45
-
46
-
[id="enhancement-rhidp-6723"]
44
+
With this update, the `@redhat-developer/red-hat-developer-hub-theme` package is replaced with the plugin version from the `rhdh-plugins` repository to improve theme integration and visual consistency. Minor UI enhancements include updated border radius on cards.
45
+
46
+
[id="enhancement-rhidp-6723"]
47
47
== Improved Role-based access control (RBAC) usability and consistency
48
48
This release includes several enhancements to improve the usability and consistency of the RBAC experience:
49
49
@@ -53,76 +53,76 @@ This release includes several enhancements to improve the usability and consiste
53
53
* Improved layout and labeling in the Conditional Access sidebar.
54
54
* Preserved typed input in search fields when selecting users, groups, or plugins.
55
55
56
-
These changes aim to create a more intuitive and seamless role management workflow.
57
-
58
-
[id="feature-rhidp-6758"]
56
+
These changes aim to create a more intuitive and seamless role management workflow.
57
+
58
+
[id="feature-rhidp-6758"]
59
59
== Introducing plugin management by using Extensions
60
60
61
-
In this release, {product-short} administrators can configure dynamic plugins directly within the Extensions UI. Administrators can now enable, disable, install, or edit the configuration of dynamic plugins on the Extensions Details Page.
61
+
In this release, {product-short} administrators can configure dynamic plugins directly within the Extensions UI. Administrators can enable, disable, install, or edit the configuration of dynamic plugins on the Extensions Details Page.
62
62
63
63
This is an opt-in feature that must be enabled by configuration, and it is intended for testing and development environments only; it is not recommended for production use.
64
64
65
-
This release requires a single replica deployment and uses a persistent volume claim (PVC) for the dynamic plugin configuration file. The {product-short} backend does not automatically restart when you save configuration changes. You must restart the {product-short} application for any dynamic plugin configuration updates to take effect.
66
-
67
-
[id="feature-rhidp-6963"]
65
+
This release requires a single replica deployment and uses a persistent volume claim (PVC) for the dynamic plugin configuration file. The {product-short} backend does not automatically restart when you save configuration changes. You must restart the {product-short} application for any dynamic plugin configuration updates to take effect.
66
+
67
+
[id="feature-rhidp-6963"]
68
68
== Dynamic plugins now fully supported and a new command-line tool released.
69
69
70
-
Backend dynamic plugins have reached General Availability (GA). A new command-line tool, `@red-hat-developer-hub/cli` (rhdh-cli), has been released for building and packaging these plugins. As a result, the `@janus-idp/cli` is now officially deprecated. All users should migrate their build processes to `@red-hat-developer-hub/cli` to maintain support and receive future updates.
71
-
72
-
[id="feature-rhidp-7018"]
70
+
Backend dynamic plugins have reached General Availability (GA). A new command-line tool, `@red-hat-developer-hub/cli` (rhdh-cli), has been released for building and packaging these plugins. As a result, the `@janus-idp/cli` is now officially deprecated. All users should migrate their build processes to `@red-hat-developer-hub/cli` to maintain support and receive future updates.
71
+
72
+
[id="feature-rhidp-7018"]
73
73
== Quick start for platform engineers
74
74
75
75
{product-very-short} 1.7 introduces the new Administrator Quick Start guide, a feature designed to streamline the initial setup and configuration process for platform engineers. This guided, interactive experience appears automatically on an administrator's first login, providing clear, step-by-step instructions for essential platform tasks. The goal is to significantly reduce onboarding time and help you configure your {product-very-short} instance with confidence.
76
76
77
-
Quick start tracks your progress, offers context-aware help that follows you across configuration pages, and can be dismissed and reopened from the header at any time. This guide ensures a confident, efficient, and structured onboarding experience. Note that when permissions are enabled, this feature is currently available for administrators only, with support for other roles planned for future versions.
78
-
79
-
[id="feature-rhidp-7106"]
77
+
Quick start tracks your progress, offers context-aware help that follows you across configuration pages, and can be dismissed and reopened from the header at any time. This guide ensures a confident, efficient, and structured onboarding experience. Note that when permissions are enabled, this feature is currently available for administrators only, with support for other roles planned for future versions.
78
+
79
+
[id="feature-rhidp-7106"]
80
80
== Improved global header UX
81
81
82
-
With this release, you can display a user avatar in the profile dropdown in the global header.
83
-
84
-
[id="feature-rhidp-7262"]
82
+
With this release, you can display a user avatar in the profile dropdown in the global header.
83
+
84
+
[id="feature-rhidp-7262"]
85
85
== Improved look and feel of {product-short}
86
86
87
-
With this update, the look and feel of {product-short} has been updated to better match the visual style of PatternFly 6 and improve alignment with the {company} product portfolio.
88
-
89
-
[id="feature-rhidp-7306"]
90
-
== Versioning for software templates
87
+
With this update, the look and feel of {product-short} has been updated to better match the visual style of PatternFly 6 and improve alignment with the {company} product portfolio.
91
88
92
-
{product-very-short} has been enhanced to provide crucial traceability, allowing users to easily identify the template version used to create a specific component. This enhancement helps determine if an older entity needs updating or if a bug is linked to a particular template version.
89
+
[id="feature-rhidp-7306"]
90
+
== Versioning for Software Templates
93
91
94
-
Scaffolder templates can now be versioned using the backstage.io/template-version annotation and the `catalog:template:version` action. When used with the `catalog:template:version` action, the annotation of the template is applied to the generated catalog entity.
95
-
96
-
[id="feature-rhidp-7561"]
92
+
{product-very-short} has been enhanced to provide crucial traceability, allowing users to easily identify the template version used to create a specific component. This enhancement helps determine if an older entity needs updating or if a bug is linked to a particular Software Template version.
93
+
94
+
Scaffolder templates can now be versioned using the backstage.io/template-version annotation and the `catalog:template:version` action. When used with the `catalog:template:version` action, the annotation of the template is applied to the generated catalog entity.
95
+
96
+
[id="feature-rhidp-7561"]
97
97
== Support for high availability in {eks-brand-name}
98
98
99
-
{product} now supports high availability setups in {eks-brand-name} ({eks-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.
99
+
{product} supports high availability setups in {eks-brand-name} ({eks-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.
100
+
101
+
For more information, see {configuring-book-link}#HighAvailability[_Configuring high availability in {product}_].
100
102
101
-
For more information, see {configuring-book-link}#HighAvailability[_Configuring high availability in {product}_].
102
-
103
-
[id="feature-rhidp-7610"]
103
+
[id="feature-rhidp-7610"]
104
104
== Adoption Insights in {product}
105
105
106
106
In this release, the Adoption Insights plugin is fully supported and enabled by default. The Adoption Insights plugin provides key metrics and trends to help you understand {product-short} usage.
107
107
108
108
If you have an existing Adoption Insights plugin custom configuration with GitHub Container registry images already set up, you can upgrade to the latest version to omit configurations using GitHub Container registry images.
109
-
For more information, see {adoption-insights-link}#proc-configure-adoption-insights_title-adoption-insights[Configuring the {adoption-insights-title}].
110
-
111
-
[id="feature-rhidp-7663"]
109
+
For more information, see {adoption-insights-link}#proc-configure-adoption-insights_title-adoption-insights[Configuring the {adoption-insights-title}].
110
+
111
+
[id="feature-rhidp-7663"]
112
112
== {product-short} community plugins updated to Backstage 1.39
113
113
114
-
The {product-short} community plugins have been updated to Backstage version 1.39.
115
-
116
-
[id="enhancement-rhidp-8103"]
114
+
The {product-short} community plugins have been updated to Backstage version 1.39.
115
+
116
+
[id="enhancement-rhidp-8103"]
117
117
== Improved robustness of dynamic plugin installation
118
118
119
-
Previously, the {product} would fail to start if a specified include file in dynamic plugins configuration did not exist. This update addresses the issue by logging a warning and skipping the file if it is not found.
120
-
121
-
[id="enhancement-rhidp-8588"]
119
+
Previously, the {product} would fail to start if a specified include file in dynamic plugins configuration did not exist. This update addresses the issue by logging a warning and skipping the file if it is not found.
120
+
121
+
[id="enhancement-rhidp-8588"]
122
122
== Full support for Microsoft Graph catalog plugin for user and group synchronization
123
123
124
-
{product} now fully supports the `@backstage/plugin-catalog-backend-module-msgraph` plugin, which ingests user and group entities from {azure-brand-name} Active Directory into the software catalog via the Microsoft Graph API.
125
-
This populates the catalog with your organization's directory data, ensuring that component ownership is accurately mapped when used with the Microsoft authentication provider.
126
-
127
-
128
-
124
+
{product} fully supports the `@backstage/plugin-catalog-backend-module-msgraph` plugin, which ingests user and group entities from {azure-brand-name} Active Directory into the software catalog via the Microsoft Graph API.
125
+
This populates the catalog with your organization's directory data, ensuring that component ownership is accurately mapped when used with the Microsoft authentication provider.
0 commit comments