added rn texts

Signed-off-by: Fabrice Flore-Thébault <[email protected]>

Author: themr0c

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

@@ -57,7 +57,7 @@ With this update, a conditional alias can use `$ownerRefs`.
 
 * link:https://issues.redhat.com/browse/RHIDP-4069[RHIDP-4069]
 
-== Fixed issues in 1.3
+== Fixed issues in 1.3.0
 
 [id="bug-fix-rhidp-1334"]
 === Removed unnecessary pull secret from the {product} Helm Chart

modules/release-notes/ref-release-notes-known-issues.adoc

@@ -4,20 +4,6 @@
 
 This section lists known issues in {product} {product-version}.
 
-[id="known-issue-rhidp-5342"]
-== [Helm] Cannot run two RHDH replicas on different nodes due to Multi-Attach errors on the dynamic plugins root PVC
-
-Currently, when deploying {product-short} using the Helm Chart, two replicas cannot run on different cluster nodes. This might also affect the upgrade from 1.3 to 1.4.0 if the new pod is scheduled on a different node.
-
-Possible workarounds for the upgrade include the following actions:
-* Manually scale down the number of replicas to 0 before upgrading your Helm release. 
-* Manually remove the old {product-short} pod after upgrading the Helm release. However, this would imply some application downtime.
-* Leverage a Pod Affinity rule to force the cluster scheduler to run your {product-short} pods on the same node.
-
-.Additional resources
-
-* link:https://issues.redhat.com/browse/RHIDP-5342[RHIDP-5342]
-
 [id="known-issue-rhidp-5284"]
 == Entities of repositories under a configured org in catalog-backend-module-github-org plugin are not deleted from the catalog when the imported repository is deleted from bulk imports
 
@@ -28,7 +14,7 @@ Repositories might be added to Developer Hub from various sources (like statical
 * link:https://issues.redhat.com/browse/RHIDP-5284[RHIDP-5284]
 
 [id="known-issue-rhidp-4695"]
-== [Doc] OIDC refresh token behavior 
+== OIDC refresh token behavior
 
 When using {rhsso-brand-name} or {rhbk-brand-name} as an OIDC provider, the default access token lifespan is set to 5 minutes, which corresponds to the token refresh grace period set in {product-short}. This 5-minute grace period is the threshold used to trigger a new refresh token call. Since the token is always near expiration, frequent refresh token requests will cause performance issues.
 
@@ -56,15 +42,5 @@ Permissions associated only with front-end plugins do not appear in the UI becau
 
 * link:https://issues.redhat.com/browse/RHIDP-3396[RHIDP-3396]
 
-[id="known-issue-rhidp-4695"]
-== [Doc] OIDC refresh token behavior 
-
-When using {rhsso-brand-name} or {rhbk-brand-name} as an OIDC provider, the default access token lifespan is set to 5 minutes, which corresponds to the token refresh grace period set in {product-short}. This 5-minute grace period is the threshold used to trigger a new refresh token call. Since the token is always near expiration, frequent refresh token requests will cause performance issues.
-
-This issue will be resolved in the 1.5 release. To prevent the performance issues, increase the lifespan in the {rhsso-brand-name} or {rhbk-brand-name} server by setting *Configure > Realm Settings > Access Token Lifespan* to a value greater than five minutes (preferably 10 or 15 minutes).
-
-
-.Additional resources
-* link:https://issues.redhat.com/browse/RHIDP-4695[RHIDP-4695]
 
 

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

@@ -170,5 +170,9 @@ dynamicPlugins:
 
 
 This update also introduced the ability to override core API service factories from a dynamic plugin, which can be helpful for more specialized use cases such as providing a custom ScmAuth configuration for the {product-short} frontend.
+[id="enhancement-rhidp-5833"]
+== Manage concurrent writing on install dynamic plugins [1.3.5]
+
+Previously, running multi-replica RHDH with a Persistent Volume for the Dynamic Plugins cache was not possible due to potential write conflicts. This update mitigates that risk 
 
 

modules/release-notes/single-source-release-notes.py

@@ -72,7 +72,7 @@
 for section in config['sections']:
   # Search in Jira for issues to publish defined in jira_query
   query = section["query"].format(
-    version_minor=product_version_minor,
+    version_minor=product_version_minor + '.0',
     version_patch=product_version_patch
   )
   print(query)