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-breaking-changes.adoc
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,7 @@ This section lists breaking changes in {product} {product-version}.
9
9
10
10
Prom-client metrics have been removed and replaced with OpenTelemetry metrics. As a result, the metrics port has changed from `7007` to `9464`. Deprecated metrics have also been removed. If you had dependencies on these, ensure your prometheus queries are updated. For further information, see link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.3/html-single/monitoring_and_logging/index#assembly-rhdh-observability[Monitoring and logging]
Copy file name to clipboardExpand all lines: modules/release-notes/ref-release-notes-deprecated-functionalities.adoc
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,7 @@ This section lists deprecated functionalities in {product} {product-version}.
9
9
10
10
The `./dynamic-plugins/dist/janus-idp-backstage-plugin-aap-backend-dynamic` plugin has been deprecated and will be removed in the next release. You can link:https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html-single/using_ansible_plug-ins_for_red_hat_developer_hub/index[use Ansible plug-ins for {product-very-short}] instead.
@@ -17,6 +18,7 @@ The `./dynamic-plugins/dist/janus-idp-backstage-plugin-aap-backend-dynamic` plug
17
18
18
19
With this update, you can evaluate your platform's log forwarding solutions to align with your security and compliance needs. Most of these solutions offer configurable options to minimize the loss of logs in the event of an outage.
Copy file name to clipboardExpand all lines: modules/release-notes/ref-release-notes-fixed-issues.adoc
+17Lines changed: 17 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,7 @@ Previously, the GitHub issues plugin defaulted to using the first GitHub integra
13
13
14
14
Now, GitHub issues plugin supports multiple GitHub integration hosts. It uses the well-known entity slug annotation `backstage.io/source-location` or `backstage.io/managed-by-location` to determine the appropriate GitHub integration for a component. If no integration matches the slug, the first GitHub integration is selected, maintaining the previous behavior.
@@ -57,6 +61,7 @@ Before this update, repositories were added to the {product-short} from various
57
61
58
62
With this update, an alert on the deletion icon notifies the user to modify the source (either the `catalog-info` within the repository or the `app-config.yaml` file if the file originates from there) to remove the catalog entity.
@@ -68,6 +73,7 @@ Before this update, the custom resources in Kubernetes configuration were pre-co
68
73
69
74
This update removes the pre-configured custom resources from the Kubernetes configuration. Therefore, users can customize resources to the Kubernetes configuration based on their requirements, preventing unrelated warnings from appearing.
@@ -101,6 +109,7 @@ Before this update, scaling the deployment to more than one pod caused Role-Base
101
109
102
110
With this update, RBAC roles are now properly synced across all pods, with Redis cache and traffic routing configured to ensure consistency across the deployment.
@@ -112,6 +121,7 @@ Previously, the CLI examined the dependencies of embedded packages during the ex
112
121
113
122
This update changes the parent directory that the {{require}} uses from the monorepo root to the embedded package. Therefore, the dependent package found is the dependency that is most relevant to the embedded package.
@@ -124,6 +134,9 @@ Previously, the CLI failed with a message that native modules are not supported.
124
134
This update introduces two new CLI flags that help dynamic plugin developers handle native modules. Both flags accept a list of packages. The `--suppress-native-package` flag does not require the native module at runtime. It replaces the native module with an empty package that displays an error. The `--allow-native-package` flag instructs the CLI to allow the native package during checks, and tests a plugin that uses a native module.
@@ -146,6 +160,7 @@ Previously, the `export-dynamic-plugin` failed with an error that the `stdout ma
146
160
147
161
With this update, the CLI redirects the output of the {{yarn install}} command it performs during the export process to a file. Therefore, a successful completion of the {{yarn install}} command and verification of the `export-dynamic-plugin`, cleans up the file. The file is available for troubleshooting when the dynamic plugin validation checks fail.
@@ -157,6 +172,7 @@ Previously, exporting a plugin that has not been updated to a newer backstage ve
157
172
158
173
With this update, an `--ignore-version-check` flag accepts a list of package names causing the CLI to selectively ignore the semver check the CLI performs when evaluating the plugin package dependencies. Therefore, a plugin that has not been updated works because it relies on unchanged interfaces and functions.
@@ -166,6 +182,7 @@ With this update, an `--ignore-version-check` flag accepts a list of package nam
166
182
167
183
With this update, you are now required to enable both `./dynamic-plugins/dist/backstage-community-tech-radar` and `./dynamic-plugins/dist/backstage-community-tech-radar-backend-dynamic` to use the Tech Radar plugin. You must configure additional settings depending on where you choose to load the JSON data for the plugin.
Copy file name to clipboardExpand all lines: modules/release-notes/ref-release-notes-known-issues.adoc
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,8 @@ This section lists known issues in {product} {product-version}.
7
7
[id="known-issue-rhidp-3396"]
8
8
== Topology plugin permission is not displayed in the RBAC front-end UI
9
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'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 Topology (`topology.view.read`), Tekton (`tekton.view.read`), ArgoCD (`argocd.view.read`), and Quay (`quay.view.read`).
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'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 Topology (`topology.view.read`), Tekton (`tekton.view.read`), ArgoCD (`argocd.view.read`), and Quay (`quay.view.read`).
Copy file name to clipboardExpand all lines: modules/release-notes/ref-release-notes-new-features.adoc
+7-9Lines changed: 7 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,26 +42,27 @@ Identify the flavor of Backstage that is running. Default value: `rhdh`
42
42
43
43
44
44
[id="feature-rhidp-4419"]
45
-
== Ability to manage PVCs in RHDH Operator
45
+
== [Doc] Document how to manage PVCs in RHDH Operator
46
+
47
+
= Ability to manage PVCs in RHDH Operator
46
48
47
49
You can now mount directories from pre-created PersistentVolumeClaims (PVCs) using the `spec.application.extraFiles.pvcs` field, while configuring RHDH Operator.
48
50
For more information, see link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.3/html-single/administration_guide_for_red_hat_developer_hub/index#proc-rhdh-deployment-config_assembly-admin-templates[Persistent Volume Claim (PVC)].
49
51
50
-
51
52
[id="feature-rhidp-4805"]
52
53
== Authenticating with {rhbk-brand-name}
53
54
54
55
With this update, you can use {rhbk-brand-name} as an authentication provider. The Keycloak plugin will now support ingesting users and groups with {rhbk-brand-name}. For more details, see link:https://docs.redhat.com/en/documentation/red_hat_build_of_keycloak/26.0/html-single/getting_started_guide/index#getting-started-zip-start-red-hat-build-of-keycloak[Authentication with {rhbk-brand-name}].
55
56
56
-
57
57
[id="feature-rhidp-4806"]
58
-
== Ability to install third-party plugins in {product-very-short}
58
+
== [Docs] Document how to install 3rd party plugins to RHDH
59
+
60
+
= Ability to install third-party plugins in {product-very-short}
59
61
60
62
You can now install third-party plugins in {product} without rebuilding the {product-very-short} application.
61
63
62
64
For more information, see link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.3/html-single/introduction_to_plugins/index[Third party plugins].
63
65
64
-
65
66
[id="feature-rhidp-4853"]
66
67
== Plugins with updated scope
67
68
@@ -189,7 +190,4 @@ With this update, the `backstage-plugin-catalog-backend-module-logs` is enabled
189
190
[id="feature-rhidp-5218"]
190
191
== {rhsso-brand-name} `7.6` is deprecated as an authentication provider
191
192
192
-
{rhsso-brand-name} ({rhsso}) `7.6` is deprecated as an authentication provider. You can continue to use {rhsso} until the end of maintenance support. For details, see link:https://access.redhat.com/support/policy/updates/jboss_notes/#p_sso[RHSSO lifecycle dates]. As an alternative, migrate to {rhbk-brand-name} `v24`.
193
-
194
-
195
-
193
+
{rhsso-brand-name} ({rhsso}) `7.6` is deprecated as an authentication provider. You can continue to use {rhsso} until the end of maintenance support. For details, see link:https://access.redhat.com/support/policy/updates/jboss_notes/#p_sso[RHSSO lifecycle dates]. As an alternative, migrate to {rhbk-brand-name} `v24`.
0 commit comments