Skip to content

Commit ee990c5

Browse files
jmagakjmagak
committed
Update release note texts
1 parent 18013df commit ee990c5

9 files changed

+18
-31
lines changed

‎assemblies/assembly-release-notes-fixed-issues.adoc‎

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,6 @@ include::modules/release-notes/snip-bug-fix-rhidp-2903.adoc[leveloffset=+1]
1414
include::modules/release-notes/snip-bug-fix-rhidp-3931.adoc[leveloffset=+1]
1515

1616

17-
include::modules/release-notes/snip-bug-fix-rhidp-4181.adoc[leveloffset=+1]
18-
19-
2017
include::modules/release-notes/snip-bug-fix-rhidp-4240.adoc[leveloffset=+1]
2118

2219

‎modules/release-notes/snip-bug-fix-rhidp-2727.adoc‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
[id="bug-fix-rhidp-2727"]
2-
= Github issues plugin now supports multiple Github integration hosts
2+
= GitHub issues plugin supports multiple GitHub integration hosts
33

4-
Before this update, Github issues plugin used the first Github integration it found for all components. This prevented the plugin from being properly used when multiple Github integration hosts were present.
4+
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.
55

6-
With this update, Github issues plugin now 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 will be selected, maintaining the previous behavior.
6+
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.
77

88
.Additional resources
99
* link:https://issues.redhat.com/browse/RHIDP-2727[RHIDP-2727]

‎modules/release-notes/snip-bug-fix-rhidp-2903.adoc‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
[id="bug-fix-rhidp-2903"]
2-
= All API documentation now defined in the 3scale backend plugin
2+
= All API documentation is defined in the 3scale backend plugin
33

4-
Before this update, not all API documentation defined in the 3scale backend plugin were available in the backstage.
4+
Previously, some API documentation defined in the 3scale backend plugin was not accessible in {product-very-short}.
55

6-
With this update, all API documentation defined in the 3scale backend plugin are imported and merged in the backstage.
6+
With this update, all API documentation defined in the 3scale backend plugin is imported and merged in the {product-very-short}.
77

88
.Additional resources
99
* link:https://issues.redhat.com/browse/RHIDP-2903[RHIDP-2903]

‎modules/release-notes/snip-bug-fix-rhidp-3931.adoc‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
[id="bug-fix-rhidp-3931"]
22
= Added alert on the deletion icon during bulk imports
33

4-
Before this update, repositories would be added to Developer Hub from various sources (like statically in an app-config file or dynamically when enabling GitHub discovery). By design, the bulk import plugin would only track repositories that are accessible from the configured GitHub integrations. When both the Bulk Import and the GitHub Discovery plugins were enabled, the repositories the latter discovers would be listed in the Bulk Import pages. However, attempting to delete a repository added by the discovery plugin from the Bulk Import Jobs would have no effect, as any entities registered by the discovery plugin or app-config would still be present in the Developer Hub catalog.
4+
Before this update, repositories were added to {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.
55

6-
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 if the file originates from there) to remove the catalog entity.
6+
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.
77

88
.Additional resources
99
* link:https://issues.redhat.com/browse/RHIDP-3931[RHIDP-3931]

‎modules/release-notes/snip-bug-fix-rhidp-4181.adoc‎

Lines changed: 0 additions & 10 deletions
This file was deleted.

‎modules/release-notes/snip-bug-fix-rhidp-4240.adoc‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
[id="bug-fix-rhidp-4240"]
2-
= Removed the pre-configured custom resources from the k8s configuration
2+
= Removed the pre-configured custom resources from the Kubernetes configuration
33

4-
Before this update, the custom resources in k8s configuration were pre-configured. As a result, users could see tekton warnings without configuring the custom resources in k8s.
4+
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.
55

6-
With this update, the pre-configured custom resources from the k8s configuration are removed. Therefore, users can custom resources to the Kubernetes configuration based on their requirements, preventing unrelated warnings from appearing.
6+
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.
77

88

99
.Additional resources

‎modules/release-notes/snip-bug-fix-rhidp-4734.adoc‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
[id="bug-fix-rhidp-4734"]
2-
= Removed RBAC API inconsistency when scaling deployment to above 1 pod
2+
= Resolved RBAC API inconsistency when scaling deployments to more than one pod
33

4-
Before this update, when scaling the deployment to above 1 pod, RBAC roles were not synced. Only the pod that creates the resource would be able to serve it afterwards.
4+
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.
55

66
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.
77

‎modules/release-notes/snip-bug-fix-rhidp-5120.adoc‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
[id="bug-fix-rhidp-5120"]
2-
= Fixed the techdoc text selection during reporting a techdoc issue
2+
= Resolved the issue with text selection when reporting a TechDoc issue
33

4-
Before this update, 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.
4+
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.
55

6-
With this update, users can select texts when reporting a documentation (techdoc) issue.
6+
With this update, users can select texts when reporting a documentation (TechDoc) issue.
77

88

99
.Additional resources

‎modules/release-notes/snip-known-issue-rhidp-3396.adoc‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
[id="known-issue-rhidp-3396"]
2-
= Topology plugin permission does not show up in RBAC frontend UI
2+
= Topology plugin permission is not displayed in the RBAC front-end UI
33

4-
Some permissions that only have frontend plugins will not show up in the UI due to a requirement of needing a backend plugin to expose the permission framework's wellknow endpoint. As a workaround, you can either apply these permissions through the use of the CSV file or by directly calling the REST API of the RBAC backend plugin. Known plugins affected are Topology topology.view.read, Tekton tekton.view.read, ArgoCD argocd.view.read, and Quay quay.view.read.
4+
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`).
55

66
.Additional resources
77
* link:https://issues.redhat.com/browse/RHIDP-3396[RHIDP-3396]

0 commit comments

Comments
 (0)