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
Previously, the GitHub issues plugin defaulted to using the first GitHub integration it detected for all components. This behavior made it incompatible with setups involving multiple GitHub integration hosts.
13
-
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.
12
+
Previously, the GitHub issues plugin defaulted to using the first GitHub integration it detected for all components. This behavior made it incompatible with setups involving multiple GitHub integration hosts.
13
+
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.
Previously, when deploying with the Helm Chart, there could be a mismatch between the Route hostname and the `baseUrl` fields added to the generated app-config ConfigMap. This could sometimes cause failure to authenticate against some providers due to an origin mismatch.
34
-
33
+
Previously, when deploying with the Helm Chart, there could be a mismatch between the Route hostname and the `baseUrl` fields added to the generated app-config ConfigMap. This could sometimes cause failure to authenticate against some providers due to an origin mismatch.
34
+
35
35
This update fixes this issue by ensuring no mismatch between those values.
@@ -50,9 +50,9 @@ With this update, disabling the RBAC backend plugin no longer creates roles and
50
50
[id="bug-fix-rhidp-3931"]
51
51
=== Added alert on the deletion icon during bulk imports
52
52
53
-
Before this update, repositories were added to the {product-short} from various sources, such as `app-config` files or GitHub discovery. The Bulk Import plugin only tracked repositories accessible using the configured GitHub integrations. When both plugins were enabled, repositories discovered by GitHub Discovery appeared on Bulk Import pages. However, deleting these repositories from Bulk Import Jobs had no effect, as entities from discovery or `app-config.yaml` file remained in the {product-short} catalog.
54
-
55
-
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.
53
+
Before this update, repositories were added to the {product-short} from various sources, such as `app-config` files or GitHub discovery. The Bulk Import plugin only tracked repositories accessible using the configured GitHub integrations. When both plugins were enabled, repositories discovered by GitHub Discovery appeared on Bulk Import pages. However, deleting these repositories from Bulk Import Jobs had no effect, as entities from discovery or `app-config.yaml` file remained in the {product-short} catalog.
54
+
55
+
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.
@@ -61,8 +61,8 @@ With this update, an alert on the deletion icon notifies the user to modify the
61
61
[id="bug-fix-rhidp-4240"]
62
62
=== Removed the pre-configured custom resources from the Kubernetes configuration
63
63
64
-
Before this update, the custom resources in Kubernetes configuration were pre-configured. As a result, users could see Tekton warnings without configuring the custom resources in Kubernetes.
65
-
64
+
Before this update, the custom resources in Kubernetes configuration were pre-configured. As a result, users could see Tekton warnings without configuring the custom resources in Kubernetes.
65
+
66
66
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.
@@ -91,8 +91,8 @@ With this update, the RBAC Backend plugin now starts successfully in version `5.
91
91
[id="bug-fix-rhidp-4734"]
92
92
=== Resolved RBAC API inconsistency when scaling deployments to more than one pod
93
93
94
-
Before this update, scaling the deployment to more than one pod caused RBAC roles to remain unsynced, allowing only the pod that created the resource to serve it.
95
-
94
+
Before this update, scaling the deployment to more than one pod caused RBAC roles to remain unsynced, allowing only the pod that created the resource to serve it.
95
+
96
96
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.
@@ -101,8 +101,8 @@ With this update, RBAC roles are now properly synced across all pods, with Redis
101
101
[id="bug-fix-rhidp-5014"]
102
102
=== `export-dynamic-plugin` fails to find dependencies nested deeper than one level in `node_modules`
103
103
104
-
Previously, the CLI examined the dependencies of embedded packages during the export process to know if other packages should be embedded. One of the methods was calling {{require}} when the CLI encountered a built embedded package, which was the case when wrapping an existing plugin.
105
-
104
+
Previously, the CLI examined the dependencies of embedded packages during the export process to know if other packages should be embedded. One of the methods was calling {{require}} when the CLI encountered a built embedded package, which was the case when wrapping an existing plugin.
105
+
106
106
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.
@@ -111,11 +111,11 @@ This update changes the parent directory that the {{require}} uses from the mono
111
111
[id="bug-fix-rhidp-5062"]
112
112
=== `suppress-native-package` and `allow-native-package` flags to handle native modules
113
113
114
-
Previously, the CLI failed with a message that native modules are not supported.
115
-
116
-
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.
117
-
118
-
114
+
Previously, the CLI failed with a message that native modules are not supported.
115
+
116
+
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.
@@ -124,8 +124,8 @@ This update introduces two new CLI flags that help dynamic plugin developers han
124
124
[id="bug-fix-rhidp-5120"]
125
125
=== Resolved the issue with text selection when reporting a TechDoc issue
126
126
127
-
Previously, the feature to report a documentation (TechDoc) issue failed. Therefore, when a user selected a text in a TechDoc, a large icon appeared instead of a tooltip button.
128
-
127
+
Previously, the feature to report a documentation (TechDoc) issue failed. Therefore, when a user selected a text in a TechDoc, a large icon appeared instead of a tooltip button.
128
+
129
129
With this update, users can select texts when reporting a documentation (TechDoc) issue.
@@ -134,8 +134,8 @@ With this update, users can select texts when reporting a documentation (TechDoc
134
134
[id="bug-fix-rhidp-5136"]
135
135
=== Resolved the `stdout maxBuffer` error
136
136
137
-
Previously, the `export-dynamic-plugin` failed with an error that the `stdout maxBuffer` length was exceeded.
138
-
137
+
Previously, the `export-dynamic-plugin` failed with an error that the `stdout maxBuffer` length was exceeded.
138
+
139
139
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.
@@ -144,13 +144,19 @@ With this update, the CLI redirects the output of the {{yarn install}} command i
144
144
[id="bug-fix-rhidp-5141"]
145
145
=== Added an `--ignore-version-check` flag
146
146
147
-
Previously, exporting a plugin that has not been updated to a newer backstage version failed due to a semver check performed on dependencies of the dynamic plugin package.
148
-
147
+
Previously, exporting a plugin that has not been updated to a newer backstage version failed due to a semver check performed on dependencies of the dynamic plugin package.
148
+
149
149
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.
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.
This section lists Technology Preview features in {product}{product-version}.
6
-
7
-
[IMPORTANT]
8
-
====
9
-
Technology Preview features provide early access to upcoming product innovations, enabling you to test functionality and provide feedback during the development process.
10
-
However, these features are not fully supported under Red Hat Subscription Level Agreements, may not be functionally complete, and are not intended for production use.
11
-
As Red Hat considers making future iterations of Technology Preview features generally available, we will attempt to resolve any issues that customers experience when using these features.
12
-
See: link:https://access.redhat.com/support/offerings/techpreview/[Technology Preview support scope].
13
-
====
14
-
15
-
[id="technology-preview-rhidp-5070"]
16
-
== Version Compatibility Matrix
17
-
1
+
:_content-type: REFERENCE
2
+
[id="technology-preview"]
3
+
= Technology Preview
4
+
5
+
This section lists Technology Preview features in {product}{product-version}.
6
+
7
+
[IMPORTANT]
8
+
====
9
+
Technology Preview features provide early access to upcoming product innovations, enabling you to test functionality and provide feedback during the development process.
10
+
However, these features are not fully supported under Red Hat Subscription Level Agreements, may not be functionally complete, and are not intended for production use.
11
+
As Red Hat considers making future iterations of Technology Preview features generally available, we will attempt to resolve any issues that customers experience when using these features.
12
+
See: link:https://access.redhat.com/support/offerings/techpreview/[Technology Preview support scope].
13
+
====
14
+
15
+
[id="technology-preview-rhidp-5070"]
16
+
== Version Compatibility Matrix
17
+
18
18
The following tables list products and their versions compatible with {product-short} {product-version}:
19
19
20
20
.Platforms compatibility matrix
@@ -44,9 +44,9 @@ The following tables list products and their versions compatible with {product-s
0 commit comments