Repository: migtools/mta-documentation
Pull request #146: Release notes for 7.3.0
Author: login: mpershina
Created: 2025-04-17T10:36:24Z | Merged: 2025-05-22T10:27:09Z

The progress is tracked under [MTA-4516](https://issues.redhat.com/browse/MTA-4516)

Preview: https://mpershina.github.io/Previews/MTA/7.3.0-release-notes.html


Diff:
diff --git a/docs/release-notes/master.adoc b/docs/release-notes/master.adoc
index 079e44d5..3cfedc73 100644
--- a/docs/release-notes/master.adoc
+++ b/docs/release-notes/master.adoc
@@ -21,8 +21,13 @@ include::topics/making-open-source-more-inclusive.adoc[]
 [id="mta-7-3-0"]
 == {ProductShortName} 7.3.0
 
+include::topics/ref_new-features-7-3-0.adoc[leveloffset=+2]
+
+include::topics/ref_fixed-issues-7-3-0.adoc[leveloffset=+2]
+
 include::topics/ref_known-issues-7-3-0.adoc[leveloffset=+2]
 
+
 [id="mta-7-2-2"]
 == {ProductShortName} 7.2.2
 
diff --git a/docs/topics/ref_fixed-issues-7-3-0.adoc b/docs/topics/ref_fixed-issues-7-3-0.adoc
new file mode 100644
index 00000000..a2949548
--- /dev/null
+++ b/docs/topics/ref_fixed-issues-7-3-0.adoc
@@ -0,0 +1,15 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-05-12
+
+:_mod-docs-content-type: REFERENCE
+
+[id="fixed-issues-7-3-0_{context}"]
+= Fixed issues
+
+This section provides the following bug fixes and resolves issues and other problems that have a significant impact on the {ProductFullName} 7.3.0.
+
+.MTA CLI now excludes the `target` folder when analyzing compiled Java Maven projects
+Previously, for compiled Java Maven projects, the {ProductShortName} CLI included incidents by analyzing the `target` folder. This generated different reports for Java Maven projects before and after running the `mvn-clean-package` command. This issue has been resolved in {ProductShortName} 7.3.0. link:https://issues.redhat.com/browse/MTA-5078[(MTA-5078)]
+
+.Application credential update now triggers a new discovery task
+Previously, when you update the source or Maven credential for an application, a new discovery task was not triggered in the {ProductShortName} {WebName}. This issue has been resolved in {ProductShortName} 7.3.0. link:https://issues.redhat.com/browse/MTA-5121[(MTA-5121)]
diff --git a/docs/topics/ref_known-issues-7-3-0.adoc b/docs/topics/ref_known-issues-7-3-0.adoc
index 6616b6de..c5787972 100644
--- a/docs/topics/ref_known-issues-7-3-0.adoc
+++ b/docs/topics/ref_known-issues-7-3-0.adoc
@@ -1,4 +1,6 @@
-:_template-generated: 2024-12-04
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-29
+
 :_mod-docs-content-type: REFERENCE
 
 [id="known-issues-7-3-0_{context}"]
@@ -6,9 +8,7 @@
 
 This section provides highlighted known issues in {ProductFullName} version 7.3.0.
 
-.Non-Java applications are analyzed in containerless mode in the {ProductShortName} CLI
-When you analyze non-Java applications, {ProductShortName} initiates the analysis in containerless mode. Workaround: set the `--run-local=false` flag to analyze non-Java applications. link:https://issues.redhat.com/browse/MTA-5068[MTA-5068]
-=======
+
 .`.NET` Framework application analysis fails in the {ProductShortName} {CLIName} 
 When you analyze `.NET` Framework applications in Windows containers using the {ProductShortName} {CLIName}, the analysis fails for the following environment variables: 
 
@@ -18,4 +18,25 @@ When you analyze `.NET` Framework applications in Windows containers using the {
 
 Workaround: Use the following version of the Dotnet provider image:
 `set DOTNET_PROVIDER_IMG=quay.io/konveyor/dotnet-external-provider:v0.5.0` 
-link:https://issues.redhat.com/browse/MTA-5203[(MTA-5203)]
\ No newline at end of file
+
+link:https://issues.redhat.com/browse/MTA-5203[(MTA-5203)]
+
+.Non-Java applications are analyzed in containerless mode in the {ProductShortName} CLI
+When you analyze non-Java applications, {ProductShortName} initiates the analysis in containerless mode. 
+
+Workaround: set the `--run-local=false` flag to analyze non-Java applications. link:https://issues.redhat.com/browse/MTA-5068[(MTA-5068)]
+
+
+.Application analysis fails to get a list of dependencies for Node.js in the {ProductShortName} UI
+
+When you run an application analysis for the Node.js language provider by using the {ProductShortName} user-interface (UI), the analysis completes with the following error is displayed in the analysis log:
+
+----
+level=error msg="failed to get list of dependencies for provider" error="dependency provider path not set" provider=nodejs'
+----
+
+Workaround: Set the `Analysis Mode` setting to `source-only`. 
+
+NOTE: The Node.js provider does not have a dependency capability. Therefore, a dependency list cannot be generated. The same applies for the Python provider.
+ 
+(link:https://issues.redhat.com/browse/MTA-5070[MTA-5070])
\ No newline at end of file
diff --git a/docs/topics/ref_new-features-7-3-0.adoc b/docs/topics/ref_new-features-7-3-0.adoc
new file mode 100644
index 00000000..4331cf83
--- /dev/null
+++ b/docs/topics/ref_new-features-7-3-0.adoc
@@ -0,0 +1,48 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+
+.Asset generation is now available in {ProductShortName} CLI
+
+Starting with {ProductShortName} {ProductVersion}, you can run the `discover` and `generate` commands in the {CLIName}: 
+
+* The `discover` command generates the discover manifest that preserves the platform and runtime configurations defined in the Cloud Foundry (CF) application manifest.
+* The `generate` command uses the discover manifest to generate the deployment manifest in a Kubernetes-native format to prepare it for {ocp-full} deployments. You can also use the command to generate non-Kubernetes manifests such as a Dockerfile.
+
+:FeatureName: Asset generation
+include::snippets/developer-preview-admonition.adoc[]
+
+(link:https://issues.redhat.com/browse/MTA-4610[MTA-4610])
+
+.{ProductShortName} now uses Red Hat Build of Keycloak for user authentication
+
+{ProductShortName} {ProductVersion} now uses `{rhbk-first}` instance for user authentication and authorization. The {ProductShortName} Operator manages the `{rhbk-short}` instance and configures a dedicated realm with necessary roles and permissions. For `{rhbk-short}`, the secret and the pod name has changed. The pod name for {rhbk-short} is changed to `rhbk-operator`. (link:https://issues.redhat.com/browse/MTA-4540[MTA-4540])
+
+.Listing all languages in an application is now available
+
+In {ProductShortName} {ProductVersion}, you can list all languages in an application by using the `--list-languages` flag in the {CLIName}. The listed language that has no supported providers requires a custom rule set and the --`override-provider-settings` flag when you analyze the application.
+
+:FeatureName: Listing all languages in an application
+include::snippets/developer-preview-admonition.adoc[]
+
+(link:https://issues.redhat.com/browse/MTA-4798[MTA-4798])
+
+
+.Support for Python and Node.js language providers is now available
+
+In addition to the Java and Go language providers, support for the Python and Node.js language providers is now available for the application analysis in {ProductShortName} 7.3.0. As a result, you can now perform the following actions for these providers in the {ProductShortName} user-interface (UI):
+
+* Add custom migration targets. 
+* Run custom rules. 
+
+:FeatureName: Support for Python and Node.js language providers
+include::snippets/technology-preview-admonition.adoc[]
+
+(link:https://issues.redhat.com/browse/MTA-4542[MTA-4542])
\ No newline at end of file


Reviews:
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-23T10:16:12Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-23T10:34:16Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-23T10:39:27Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-23T10:39:41Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-23T10:41:59Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-23T10:42:21Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-23T10:43:35Z
user: login: Pkylas007
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-23T12:11:38Z
user: login: Pkylas007
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-23T12:11:53Z
user: login: Pkylas007
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-23T12:12:35Z
user: login: Pkylas007
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-23T12:13:05Z
user: login: Pkylas007
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-23T12:15:28Z
user: login: Pkylas007
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-23T12:18:09Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-23T14:18:16Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-23T16:08:01Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-23T16:08:28Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-23T16:09:44Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-23T16:16:05Z
user: login: Pkylas007
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-23T23:20:36Z
user: login: Pkylas007
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-23T23:31:51Z
user: login: Pkylas007
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-24T04:46:49Z
user: login: Pkylas007
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-24T05:45:02Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-25T15:10:59Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-25T15:14:28Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-25T15:15:44Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-25T15:18:00Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-25T15:18:44Z
user: login: jortel
state: COMMENTED
author_association: NONE
submitted_at: 2025-04-28T13:45:38Z
user: login: jortel
state: COMMENTED
author_association: NONE
submitted_at: 2025-04-28T13:46:54Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-28T13:53:59Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-28T13:54:38Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-28T14:00:44Z
user: login: jortel
state: COMMENTED
author_association: NONE
submitted_at: 2025-04-29T13:37:59Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-30T09:21:18Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-30T09:26:05Z
user: login: jortel
state: COMMENTED
author_association: NONE
submitted_at: 2025-04-30T12:59:38Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-30T13:05:12Z
user: login: eemcmullan
state: COMMENTED
author_association: NONE
submitted_at: 2025-04-30T19:00:09Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-05-05T12:04:16Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-05-05T12:08:34Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-05-05T12:08:36Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-05-05T12:09:14Z
user: login: Pkylas007
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-05-05T13:12:44Z
user: login: Pkylas007
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-05-05T13:15:10Z
user: login: eemcmullan
state: COMMENTED
author_association: NONE
submitted_at: 2025-05-05T14:47:08Z
user: login: eemcmullan
state: COMMENTED
author_association: NONE
submitted_at: 2025-05-05T14:47:33Z
user: login: eemcmullan
state: COMMENTED
author_association: NONE
submitted_at: 2025-05-05T14:50:10Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-05-05T15:04:54Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-05-05T15:06:11Z
user: login: Pkylas007
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-05-12T10:28:55Z
user: login: Pkylas007
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-05-12T14:56:00Z
user: login: Pkylas007
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-05-19T02:39:48Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-05-19T06:12:11Z
user: login: Pkylas007
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-05-21T12:27:33Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-05-22T07:10:54Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-05-22T07:11:08Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-05-22T07:12:00Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-05-22T07:15:09Z
user: login: Pkylas007
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-05-22T07:18:28Z
user: login: istein1
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-05-22T09:01:16Z
user: login: Pkylas007
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-05-22T09:16:35Z
user: login: Pkylas007
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-05-22T09:17:45Z
user: login: ibragins
body: LGTM
state: APPROVED
author_association: COLLABORATOR
submitted_at: 2025-05-22T09:48:58Z
user: login: abrugaro
body: LGTM, minor comment
state: APPROVED
author_association: NONE
submitted_at: 2025-05-22T09:55:03Z
user: login: mpershina
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-05-22T10:02:37Z
user: login: rromannissen
body: LGTM!
state: APPROVED
author_association: NONE
submitted_at: 2025-05-22T10:18:08Z

Review comments:
diff_hunk: @@ -0,0 +1,16 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+MTA-4540
+
+
+MTA-4549
+
+MTA-4610
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: mpershina
body: ```suggestion
MTA-4610

.Generate deployment manifest in {ProductShortName} CLI

Starting with {ProductShortName} {ProductVersion}, you can run the `discover` and `generate` commands in the {CLIName}. The `discover` command generates the discover manifest that preserves the platform and runtime configurations defined in the Cloud Foundry (CF) application manifest. The `generate` command uses the discover manifest to generate the deployment manifest in a Kubernetes-native format so that, it is ready for {ocp-full} deployments.

.{ProductShortName} uses Red Hat Build of Keycloak for user authentication

The {ProductShortName} {ProductVersion} uses `{rhbk-first}` instance for user authentication and authorization.The {ProductShortName} operator manages the `{rhbk-short}` instance and configures a dedicated realm with necessary roles and permissions. For `{rhbk-short}`, the secret and the pod name has changed. The pod name for {rhbk-short} is changed to `rhbk-operator`.

.List all languages in an application

In {ProductShortName} {ProductVersion}, you can list all languages in an application using the `--list-languages` flag in the {CLIName}. The listed language that has no supported providers requires a custom rule set and the --`override-provider-settings` flag when you analyze the application.
```
created_at: 2025-04-23T10:16:12Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,28 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+MTA-4540
+
+
+MTA-4549
+
+MTA-4610
+
+.Generate deployment manifest in {ProductShortName} CLI
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: mpershina
body: How about this wording to emphasize it is a new feature? I know that the section's name implies that, I'm just following our RHEL standards, hehe :-D

```suggestion
.The deployment manifest generation is now supported in the {ProductShortName} CLI
```
created_at: 2025-04-23T10:34:16Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,28 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+MTA-4540
+
+
+MTA-4549
+
+MTA-4610
+
+.Generate deployment manifest in {ProductShortName} CLI
+
+Starting with {ProductShortName} {ProductVersion}, you can run the `discover` and `generate` commands in the {CLIName}. The `discover` command generates the discover manifest that preserves the platform and runtime configurations defined in the Cloud Foundry (CF) application manifest. The `generate` command uses the discover manifest to generate the deployment manifest in a Kubernetes-native format so that, it is ready for {ocp-full} deployments.
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: mpershina
body: ```suggestion
Starting with {ProductShortName} {ProductVersion}, you can run the `discover` and `generate` commands in the {CLIName}: 

* The `discover` command generates the discover manifest that preserves the platform and runtime configurations defined in the Cloud Foundry (CF) application manifest.
* The `generate` command uses the discover manifest to generate the deployment manifest in a Kubernetes-native format to prepare it for {ocp-full} deployments.

(link:https://issues.redhat.com/browse/MTA-4610[MTA-4610]
```
created_at: 2025-04-23T10:39:27Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,28 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+MTA-4540
+
+
+MTA-4549
+
+MTA-4610
+
+.Generate deployment manifest in {ProductShortName} CLI
+
+Starting with {ProductShortName} {ProductVersion}, you can run the `discover` and `generate` commands in the {CLIName}. The `discover` command generates the discover manifest that preserves the platform and runtime configurations defined in the Cloud Foundry (CF) application manifest. The `generate` command uses the discover manifest to generate the deployment manifest in a Kubernetes-native format so that, it is ready for {ocp-full} deployments.
+
+.{ProductShortName} uses Red Hat Build of Keycloak for user authentication
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: mpershina
body: ```suggestion
.{ProductShortName} now uses Red Hat Build of Keycloak for user authentication
```
created_at: 2025-04-23T10:39:41Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,28 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+MTA-4540
+
+
+MTA-4549
+
+MTA-4610
+
+.Generate deployment manifest in {ProductShortName} CLI
+
+Starting with {ProductShortName} {ProductVersion}, you can run the `discover` and `generate` commands in the {CLIName}. The `discover` command generates the discover manifest that preserves the platform and runtime configurations defined in the Cloud Foundry (CF) application manifest. The `generate` command uses the discover manifest to generate the deployment manifest in a Kubernetes-native format so that, it is ready for {ocp-full} deployments.
+
+.{ProductShortName} uses Red Hat Build of Keycloak for user authentication
+
+The {ProductShortName} {ProductVersion} uses `{rhbk-first}` instance for user authentication and authorization.The {ProductShortName} operator manages the `{rhbk-short}` instance and configures a dedicated realm with necessary roles and permissions. For `{rhbk-short}`, the secret and the pod name has changed. The pod name for {rhbk-short} is changed to `rhbk-operator`.
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: mpershina
body: One Q to this: You mentioned that the pod name for {rhbk-short} has been changed to `rhbk-operator`. What about  the secret then?

```suggestion
{ProductShortName} {ProductVersion} now uses `{rhbk-first}` instance for user authentication and authorization. The {ProductShortName} Operator manages the `{rhbk-short}` instance and configures a dedicated realm with necessary roles and permissions. For `{rhbk-short}`, the secret and the pod name has changed. The pod name for {rhbk-short} is changed to `rhbk-operator`.
```
created_at: 2025-04-23T10:41:59Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,28 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+MTA-4540
+
+
+MTA-4549
+
+MTA-4610
+
+.Generate deployment manifest in {ProductShortName} CLI
+
+Starting with {ProductShortName} {ProductVersion}, you can run the `discover` and `generate` commands in the {CLIName}. The `discover` command generates the discover manifest that preserves the platform and runtime configurations defined in the Cloud Foundry (CF) application manifest. The `generate` command uses the discover manifest to generate the deployment manifest in a Kubernetes-native format so that, it is ready for {ocp-full} deployments.
+
+.{ProductShortName} uses Red Hat Build of Keycloak for user authentication
+
+The {ProductShortName} {ProductVersion} uses `{rhbk-first}` instance for user authentication and authorization.The {ProductShortName} operator manages the `{rhbk-short}` instance and configures a dedicated realm with necessary roles and permissions. For `{rhbk-short}`, the secret and the pod name has changed. The pod name for {rhbk-short} is changed to `rhbk-operator`.
+
+.List all languages in an application
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: mpershina
body: ```suggestion
.Listing all languages in an application is now supported
```
created_at: 2025-04-23T10:42:20Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,28 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+MTA-4540
+
+
+MTA-4549
+
+MTA-4610
+
+.Generate deployment manifest in {ProductShortName} CLI
+
+Starting with {ProductShortName} {ProductVersion}, you can run the `discover` and `generate` commands in the {CLIName}. The `discover` command generates the discover manifest that preserves the platform and runtime configurations defined in the Cloud Foundry (CF) application manifest. The `generate` command uses the discover manifest to generate the deployment manifest in a Kubernetes-native format so that, it is ready for {ocp-full} deployments.
+
+.{ProductShortName} uses Red Hat Build of Keycloak for user authentication
+
+The {ProductShortName} {ProductVersion} uses `{rhbk-first}` instance for user authentication and authorization.The {ProductShortName} operator manages the `{rhbk-short}` instance and configures a dedicated realm with necessary roles and permissions. For `{rhbk-short}`, the secret and the pod name has changed. The pod name for {rhbk-short} is changed to `rhbk-operator`.
+
+.List all languages in an application
+
+In {ProductShortName} {ProductVersion}, you can list all languages in an application using the `--list-languages` flag in the {CLIName}. The listed language that has no supported providers requires a custom rule set and the --`override-provider-settings` flag when you analyze the application.
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: mpershina
body: ```suggestion
In {ProductShortName} {ProductVersion}, you can list all languages in an application by using the `--list-languages` flag in the {CLIName}. The listed language that has no supported providers requires a custom rule set and the --`override-provider-settings` flag when you analyze the application.
```
created_at: 2025-04-23T10:43:35Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,28 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+MTA-4540
+
+
+MTA-4549
+
+MTA-4610
+
+.Generate deployment manifest in {ProductShortName} CLI
+
+Starting with {ProductShortName} {ProductVersion}, you can run the `discover` and `generate` commands in the {CLIName}. The `discover` command generates the discover manifest that preserves the platform and runtime configurations defined in the Cloud Foundry (CF) application manifest. The `generate` command uses the discover manifest to generate the deployment manifest in a Kubernetes-native format so that, it is ready for {ocp-full} deployments.
+
+.{ProductShortName} uses Red Hat Build of Keycloak for user authentication
+
+The {ProductShortName} {ProductVersion} uses `{rhbk-first}` instance for user authentication and authorization.The {ProductShortName} operator manages the `{rhbk-short}` instance and configures a dedicated realm with necessary roles and permissions. For `{rhbk-short}`, the secret and the pod name has changed. The pod name for {rhbk-short} is changed to `rhbk-operator`.
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: Pkylas007
body: I'm cannot apply the changes directly in this PR :) Yes, let's go with the changes please.
created_at: 2025-04-23T12:11:38Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,28 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+MTA-4540
+
+
+MTA-4549
+
+MTA-4610
+
+.Generate deployment manifest in {ProductShortName} CLI
+
+Starting with {ProductShortName} {ProductVersion}, you can run the `discover` and `generate` commands in the {CLIName}. The `discover` command generates the discover manifest that preserves the platform and runtime configurations defined in the Cloud Foundry (CF) application manifest. The `generate` command uses the discover manifest to generate the deployment manifest in a Kubernetes-native format so that, it is ready for {ocp-full} deployments.
+
+.{ProductShortName} uses Red Hat Build of Keycloak for user authentication
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: Pkylas007
body: Ok
created_at: 2025-04-23T12:11:53Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,28 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+MTA-4540
+
+
+MTA-4549
+
+MTA-4610
+
+.Generate deployment manifest in {ProductShortName} CLI
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: Pkylas007
body: I would prefer to retain the actionable title (Generate...) if that's ok with you.
created_at: 2025-04-23T12:12:35Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,28 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+MTA-4540
+
+
+MTA-4549
+
+MTA-4610
+
+.Generate deployment manifest in {ProductShortName} CLI
+
+Starting with {ProductShortName} {ProductVersion}, you can run the `discover` and `generate` commands in the {CLIName}. The `discover` command generates the discover manifest that preserves the platform and runtime configurations defined in the Cloud Foundry (CF) application manifest. The `generate` command uses the discover manifest to generate the deployment manifest in a Kubernetes-native format so that, it is ready for {ocp-full} deployments.
+
+.{ProductShortName} uses Red Hat Build of Keycloak for user authentication
+
+The {ProductShortName} {ProductVersion} uses `{rhbk-first}` instance for user authentication and authorization.The {ProductShortName} operator manages the `{rhbk-short}` instance and configures a dedicated realm with necessary roles and permissions. For `{rhbk-short}`, the secret and the pod name has changed. The pod name for {rhbk-short} is changed to `rhbk-operator`.
+
+.List all languages in an application
+
+In {ProductShortName} {ProductVersion}, you can list all languages in an application using the `--list-languages` flag in the {CLIName}. The listed language that has no supported providers requires a custom rule set and the --`override-provider-settings` flag when you analyze the application.
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: Pkylas007
body: Sure, thanks! Could you apply the change please?
created_at: 2025-04-23T12:13:05Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,28 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+MTA-4540
+
+
+MTA-4549
+
+MTA-4610
+
+.Generate deployment manifest in {ProductShortName} CLI
+
+Starting with {ProductShortName} {ProductVersion}, you can run the `discover` and `generate` commands in the {CLIName}. The `discover` command generates the discover manifest that preserves the platform and runtime configurations defined in the Cloud Foundry (CF) application manifest. The `generate` command uses the discover manifest to generate the deployment manifest in a Kubernetes-native format so that, it is ready for {ocp-full} deployments.
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: Pkylas007
body: Sure, thanks! May I suggest a tiny change?
```suggestion
Starting with {ProductShortName} {ProductVersion}, you can run the `discover` and `generate` commands in the {CLIName}:

* The `discover` command generates the discover manifest that preserves the platform and runtime configurations defined in the Cloud Foundry (CF) application manifest. 

* The `generate` command uses the discover manifest to generate the deployment manifest in a Kubernetes-native format to prepare it for {ocp-full} deployments.
```
created_at: 2025-04-23T12:15:28Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,28 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+MTA-4540
+
+
+MTA-4549
+
+MTA-4610
+
+.Generate deployment manifest in {ProductShortName} CLI
+
+Starting with {ProductShortName} {ProductVersion}, you can run the `discover` and `generate` commands in the {CLIName}. The `discover` command generates the discover manifest that preserves the platform and runtime configurations defined in the Cloud Foundry (CF) application manifest. The `generate` command uses the discover manifest to generate the deployment manifest in a Kubernetes-native format so that, it is ready for {ocp-full} deployments.
+
+.{ProductShortName} uses Red Hat Build of Keycloak for user authentication
+
+The {ProductShortName} {ProductVersion} uses `{rhbk-first}` instance for user authentication and authorization.The {ProductShortName} operator manages the `{rhbk-short}` instance and configures a dedicated realm with necessary roles and permissions. For `{rhbk-short}`, the secret and the pod name has changed. The pod name for {rhbk-short} is changed to `rhbk-operator`.
+
+.List all languages in an application
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: Pkylas007
body: > I would prefer List since it's an action verb in the title. What do you think?

```suggestion
.List all languages in an application
```
created_at: 2025-04-23T12:18:09Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,28 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+MTA-4540
+
+
+MTA-4549
+
+MTA-4610
+
+.Generate deployment manifest in {ProductShortName} CLI
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: mpershina
body: Hmm...I'd say that this kind of "actionable" title does suit some procedural module rather than a release note. A release note is a theoretical pice of info and that's why I'd prefer not using ing here especially because it sounds like an imperative and the user must do something, which is not the case. 
created_at: 2025-04-23T14:18:16Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,28 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+MTA-4540
+
+
+MTA-4549
+
+MTA-4610
+
+.Generate deployment manifest in {ProductShortName} CLI
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: mpershina
body: As for you suggestion ("Support to generate deployment manifest"), if you'd like to have something like that, I suggest rewording it a bit to "Support for deployment manifest generation in {ProductShortName} CLI". 
created_at: 2025-04-23T16:08:01Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,28 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+MTA-4540
+
+
+MTA-4549
+
+MTA-4610
+
+.Generate deployment manifest in {ProductShortName} CLI
+
+Starting with {ProductShortName} {ProductVersion}, you can run the `discover` and `generate` commands in the {CLIName}. The `discover` command generates the discover manifest that preserves the platform and runtime configurations defined in the Cloud Foundry (CF) application manifest. The `generate` command uses the discover manifest to generate the deployment manifest in a Kubernetes-native format so that, it is ready for {ocp-full} deployments.
+
+.{ProductShortName} uses Red Hat Build of Keycloak for user authentication
+
+The {ProductShortName} {ProductVersion} uses `{rhbk-first}` instance for user authentication and authorization.The {ProductShortName} operator manages the `{rhbk-short}` instance and configures a dedicated realm with necessary roles and permissions. For `{rhbk-short}`, the secret and the pod name has changed. The pod name for {rhbk-short} is changed to `rhbk-operator`.
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: mpershina
body: Sure, applying :)
created_at: 2025-04-23T16:08:28Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,28 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+MTA-4540
+
+
+MTA-4549
+
+MTA-4610
+
+.Generate deployment manifest in {ProductShortName} CLI
+
+Starting with {ProductShortName} {ProductVersion}, you can run the `discover` and `generate` commands in the {CLIName}. The `discover` command generates the discover manifest that preserves the platform and runtime configurations defined in the Cloud Foundry (CF) application manifest. The `generate` command uses the discover manifest to generate the deployment manifest in a Kubernetes-native format so that, it is ready for {ocp-full} deployments.
+
+.{ProductShortName} uses Red Hat Build of Keycloak for user authentication
+
+The {ProductShortName} {ProductVersion} uses `{rhbk-first}` instance for user authentication and authorization.The {ProductShortName} operator manages the `{rhbk-short}` instance and configures a dedicated realm with necessary roles and permissions. For `{rhbk-short}`, the secret and the pod name has changed. The pod name for {rhbk-short} is changed to `rhbk-operator`.
+
+.List all languages in an application
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: mpershina
body: The same situation here, we should not use imperatives in the release notes titles. These are suitable for a procedural module title as it implies there's some action the user must perform.
created_at: 2025-04-23T16:09:44Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,28 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+MTA-4540
+
+
+MTA-4549
+
+MTA-4610
+
+.Generate deployment manifest in {ProductShortName} CLI
+
+Starting with {ProductShortName} {ProductVersion}, you can run the `discover` and `generate` commands in the {CLIName}. The `discover` command generates the discover manifest that preserves the platform and runtime configurations defined in the Cloud Foundry (CF) application manifest. The `generate` command uses the discover manifest to generate the deployment manifest in a Kubernetes-native format so that, it is ready for {ocp-full} deployments.
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: mpershina
body: If the case is in the word "run", can be. I don't have a strong preference here :-) 
As for "so that, it is ready for {ocp-full} deployments" , not sure about this "so that it is ready" part. I think "to prepare" here means the same. But if you decide to use "so that it is ready", don't forget to remove the comma :-)

Let me know if you meant something else by your suggestion :-D 
created_at: 2025-04-23T16:16:05Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,28 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+MTA-4540
+
+
+MTA-4549
+
+MTA-4610
+
+.Generate deployment manifest in {ProductShortName} CLI
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: Pkylas007
body: @mpershina Shall we please agree to include:
 
```suggestion
.Support for generating deployment manifest in {ProductShortName} CLI
```
Reason: titles must not be a complete sentence. 
created_at: 2025-04-23T23:20:35Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,28 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+MTA-4540
+
+
+MTA-4549
+
+MTA-4610
+
+.Generate deployment manifest in {ProductShortName} CLI
+
+Starting with {ProductShortName} {ProductVersion}, you can run the `discover` and `generate` commands in the {CLIName}. The `discover` command generates the discover manifest that preserves the platform and runtime configurations defined in the Cloud Foundry (CF) application manifest. The `generate` command uses the discover manifest to generate the deployment manifest in a Kubernetes-native format so that, it is ready for {ocp-full} deployments.
+
+.{ProductShortName} now uses Red Hat Build of Keycloak for user authentication
+
+{ProductShortName} {ProductVersion} now uses `{rhbk-first}` instance for user authentication and authorization. The {ProductShortName} Operator manages the `{rhbk-short}` instance and configures a dedicated realm with necessary roles and permissions. For `{rhbk-short}`, the secret and the pod name has changed. The pod name for {rhbk-short} is changed to `rhbk-operator`.
+
+.List all languages in an application
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: Pkylas007
body: ```suggestion
.Support for listing all languages in an application```
Shall we please not enter full sentences in headings/titles? 
created_at: 2025-04-23T23:31:51Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,28 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+MTA-4540
+
+
+MTA-4549
+
+MTA-4610
+
+.Generate deployment manifest in {ProductShortName} CLI
+
+Starting with {ProductShortName} {ProductVersion}, you can run the `discover` and `generate` commands in the {CLIName}. The `discover` command generates the discover manifest that preserves the platform and runtime configurations defined in the Cloud Foundry (CF) application manifest. The `generate` command uses the discover manifest to generate the deployment manifest in a Kubernetes-native format so that, it is ready for {ocp-full} deployments.
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: Pkylas007
body: Oh, yeah one of the changes was an omission. I meant keeping run the commands :) "so that it is ready" lends a conversational tone. Again, each company has it's own set of "rules" :)
created_at: 2025-04-24T04:46:49Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,28 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+MTA-4540
+
+
+MTA-4549
+
+MTA-4610
+
+.Generate deployment manifest in {ProductShortName} CLI
+
+Starting with {ProductShortName} {ProductVersion}, you can run the `discover` and `generate` commands in the {CLIName}. The `discover` command generates the discover manifest that preserves the platform and runtime configurations defined in the Cloud Foundry (CF) application manifest. The `generate` command uses the discover manifest to generate the deployment manifest in a Kubernetes-native format so that, it is ready for {ocp-full} deployments.
+
+.{ProductShortName} now uses Red Hat Build of Keycloak for user authentication
+
+{ProductShortName} {ProductVersion} now uses `{rhbk-first}` instance for user authentication and authorization. The {ProductShortName} Operator manages the `{rhbk-short}` instance and configures a dedicated realm with necessary roles and permissions. For `{rhbk-short}`, the secret and the pod name has changed. The pod name for {rhbk-short} is changed to `rhbk-operator`.
+
+.List all languages in an application
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: Pkylas007
body: i have reworked the title though I'm still for actionable titles :) Those speak directly to what the customers can do instead of what we present to them.
created_at: 2025-04-24T05:45:02Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,28 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+MTA-4540
+
+
+MTA-4549
+
+MTA-4610
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: mpershina
body: ```suggestion
```
created_at: 2025-04-25T15:10:59Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,28 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+MTA-4540
+
+
+MTA-4549
+
+MTA-4610
+
+.Generate deployment manifest in {ProductShortName} CLI
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: mpershina
body: Hmm, that's interesting...I usually follow our CCS Guidelines, and there's nothing like that about that: https://source.redhat.com/groups/public/ccs/rheldocslandingpage/rhel_documentation_master_page_wiki/rhel_release_notes_ccs_guidelines_for_writers#jive_content_id_12_General_rules_for_titles.
created_at: 2025-04-25T15:14:28Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,28 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+MTA-4540
+
+
+MTA-4549
+
+MTA-4610
+
+.Generate deployment manifest in {ProductShortName} CLI
+
+Starting with {ProductShortName} {ProductVersion}, you can run the `discover` and `generate` commands in the {CLIName}. The `discover` command generates the discover manifest that preserves the platform and runtime configurations defined in the Cloud Foundry (CF) application manifest. The `generate` command uses the discover manifest to generate the deployment manifest in a Kubernetes-native format so that, it is ready for {ocp-full} deployments.
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: mpershina
body: True :-) We just try to avoid conversational tone :-D 
created_at: 2025-04-25T15:15:44Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,28 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+MTA-4540
+
+
+MTA-4549
+
+MTA-4610
+
+.Generate deployment manifest in {ProductShortName} CLI
+
+Starting with {ProductShortName} {ProductVersion}, you can run the `discover` and `generate` commands in the {CLIName}. The `discover` command generates the discover manifest that preserves the platform and runtime configurations defined in the Cloud Foundry (CF) application manifest. The `generate` command uses the discover manifest to generate the deployment manifest in a Kubernetes-native format so that, it is ready for {ocp-full} deployments.
+
+.{ProductShortName} now uses Red Hat Build of Keycloak for user authentication
+
+{ProductShortName} {ProductVersion} now uses `{rhbk-first}` instance for user authentication and authorization. The {ProductShortName} Operator manages the `{rhbk-short}` instance and configures a dedicated realm with necessary roles and permissions. For `{rhbk-short}`, the secret and the pod name has changed. The pod name for {rhbk-short} is changed to `rhbk-operator`.
+
+.List all languages in an application
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: mpershina
body: Again, I have never heard about not using full sentences in headings/titles. See my comment on the similar case above
created_at: 2025-04-25T15:18:00Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,28 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+MTA-4540
+
+
+MTA-4549
+
+MTA-4610
+
+.Generate deployment manifest in {ProductShortName} CLI
+
+Starting with {ProductShortName} {ProductVersion}, you can run the `discover` and `generate` commands in the {CLIName}. The `discover` command generates the discover manifest that preserves the platform and runtime configurations defined in the Cloud Foundry (CF) application manifest. The `generate` command uses the discover manifest to generate the deployment manifest in a Kubernetes-native format so that, it is ready for {ocp-full} deployments.
+
+.{ProductShortName} now uses Red Hat Build of Keycloak for user authentication
+
+{ProductShortName} {ProductVersion} now uses `{rhbk-first}` instance for user authentication and authorization. The {ProductShortName} Operator manages the `{rhbk-short}` instance and configures a dedicated realm with necessary roles and permissions. For `{rhbk-short}`, the secret and the pod name has changed. The pod name for {rhbk-short} is changed to `rhbk-operator`.
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: mpershina
body: ```suggestion
{ProductShortName} {ProductVersion} now uses `{rhbk-first}` instance for user authentication and authorization. The {ProductShortName} Operator manages the `{rhbk-short}` instance and configures a dedicated realm with necessary roles and permissions. For `{rhbk-short}`, the secret and the pod name has changed. The pod name for {rhbk-short} is changed to `rhbk-operator`. (link:https://issues.redhat.com/browse/MTA-4540[MTA-4540])
```
created_at: 2025-04-25T15:18:44Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,14 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-25
+
+:_mod-docs-content-type: REFERENCE
+
+[id="technology-preview-features-7-3-0_{context}"]
+= Technology preview features
+
+This part provides a list of Technology Preview features available in {ProductFullName} 7.3.0. 
+
+
+.Support for Python and Node.js providers is available as a Technology Preview.
+
+In addition to the Java and Go language providers, support for the Python and Node.js language providers is now available in {ProductShortName} 7.3.0 as a Technology Preview. You can now add custom migration targets for these providers in the {ProductShortName} user-interface (UI). (link:https://issues.redhat.com/browse/MTA-4542[MTA-4542])
path: docs/topics/ref_technology-preview-features-7-3-0.adoc
user: login: jortel
body: I would suggest framing the feature by specifically saying it is for analysis.  Most users probably don't know what _language providers_ are.
created_at: 2025-04-28T13:45:38Z
author_association: NONE
diff_hunk: @@ -0,0 +1,14 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-25
+
+:_mod-docs-content-type: REFERENCE
+
+[id="technology-preview-features-7-3-0_{context}"]
+= Technology preview features
+
+This part provides a list of Technology Preview features available in {ProductFullName} 7.3.0. 
+
+
+.Support for Python and Node.js providers is available as a Technology Preview.
+
+In addition to the Java and Go language providers, support for the Python and Node.js language providers is now available in {ProductShortName} 7.3.0 as a Technology Preview. You can now add custom migration targets for these providers in the {ProductShortName} user-interface (UI). (link:https://issues.redhat.com/browse/MTA-4542[MTA-4542])
path: docs/topics/ref_technology-preview-features-7-3-0.adoc
user: login: jortel
body: Also mention that  in addition to custom targets, user can run custom rules for python and nodejs.
created_at: 2025-04-28T13:46:54Z
author_association: NONE
diff_hunk: @@ -0,0 +1,14 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-25
+
+:_mod-docs-content-type: REFERENCE
+
+[id="technology-preview-features-7-3-0_{context}"]
+= Technology preview features
+
+This part provides a list of Technology Preview features available in {ProductFullName} 7.3.0. 
+
+
+.Support for Python and Node.js providers is available as a Technology Preview.
+
+In addition to the Java and Go language providers, support for the Python and Node.js language providers is now available in {ProductShortName} 7.3.0 as a Technology Preview. You can now add custom migration targets for these providers in the {ProductShortName} user-interface (UI). (link:https://issues.redhat.com/browse/MTA-4542[MTA-4542])
path: docs/topics/ref_technology-preview-features-7-3-0.adoc
user: login: mpershina
body: ```suggestion
.Support for Python and Node.js language providers is available as a Technology Preview.

In addition to the Java and Go language providers, support for the Python and Node.js language providers is now available for the application analysis in {ProductShortName} 7.3.0 as a Technology Preview. As a result, you can now perform the following actions for these providers in the {ProductShortName} user-interface (UI):

* Add custom migration targets. 
* Run custom rules. 

(link:https://issues.redhat.com/browse/MTA-4542[MTA-4542])
```
created_at: 2025-04-28T13:53:58Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,14 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-25
+
+:_mod-docs-content-type: REFERENCE
+
+[id="technology-preview-features-7-3-0_{context}"]
+= Technology preview features
+
+This part provides a list of Technology Preview features available in {ProductFullName} 7.3.0. 
+
+
+.Support for Python and Node.js providers is available as a Technology Preview.
+
+In addition to the Java and Go language providers, support for the Python and Node.js language providers is now available in {ProductShortName} 7.3.0 as a Technology Preview. You can now add custom migration targets for these providers in the {ProductShortName} user-interface (UI). (link:https://issues.redhat.com/browse/MTA-4542[MTA-4542])
path: docs/topics/ref_technology-preview-features-7-3-0.adoc
user: login: mpershina
body: Thanks a lot for the info! I added a suggestion below, does that work, @jortel? 
created_at: 2025-04-28T13:54:37Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,27 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+
+.Generate deployment manifest in {ProductShortName} CLI
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: mpershina
body: ```suggestion
.The deployment manifest generation is now available in {ProductShortName} CLI
```
created_at: 2025-04-28T14:00:44Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,20 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-29
+
+:_mod-docs-content-type: REFERENCE
+
+[id="known-issues-7-3-0_{context}"]
+= Known issues
+
+This section provides highlighted known issues in {ProductFullName} version 7.3.0.
+
+
+.Application analysis fails to get a list of dependencies for Node.js
+
+When you run an application analysis for the Node.js language provider, the analysis completes with the following error is displayed in the analysis log:
+
+----
+level=error msg="failed to get list of dependencies for provider" error="dependency provider path not set" provider=nodejs'
+----
+
+Currently, there is no workaround available for this issue. (link:https://issues.redhat.com/browse/MTA-5070[MTA-5070])
path: docs/topics/ref_known-issues-7-3-0.adoc
user: login: jortel
body: I _think_ the workaround is to use mode: source (only).
created_at: 2025-04-29T13:37:59Z
author_association: NONE
diff_hunk: @@ -0,0 +1,20 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-29
+
+:_mod-docs-content-type: REFERENCE
+
+[id="known-issues-7-3-0_{context}"]
+= Known issues
+
+This section provides highlighted known issues in {ProductFullName} version 7.3.0.
+
+
+.Application analysis fails to get a list of dependencies for Node.js
+
+When you run an application analysis for the Node.js language provider, the analysis completes with the following error is displayed in the analysis log:
+
+----
+level=error msg="failed to get list of dependencies for provider" error="dependency provider path not set" provider=nodejs'
+----
+
+Currently, there is no workaround available for this issue. (link:https://issues.redhat.com/browse/MTA-5070[MTA-5070])
path: docs/topics/ref_known-issues-7-3-0.adoc
user: login: mpershina
body: ```suggestion
To work around this issue, set the `Analysis Mode` setting to `source-only`. (link:https://issues.redhat.com/browse/MTA-5070[MTA-5070])
```
created_at: 2025-04-30T09:21:18Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,20 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-29
+
+:_mod-docs-content-type: REFERENCE
+
+[id="known-issues-7-3-0_{context}"]
+= Known issues
+
+This section provides highlighted known issues in {ProductFullName} version 7.3.0.
+
+
+.Application analysis fails to get a list of dependencies for Node.js
+
+When you run an application analysis for the Node.js language provider, the analysis completes with the following error is displayed in the analysis log:
+
+----
+level=error msg="failed to get list of dependencies for provider" error="dependency provider path not set" provider=nodejs'
+----
+
+Currently, there is no workaround available for this issue. (link:https://issues.redhat.com/browse/MTA-5070[MTA-5070])
path: docs/topics/ref_known-issues-7-3-0.adoc
user: login: mpershina
body: @jortel, added a suggestion below, please, check. Just wanted to ask, is it `source-only` or `source (only)`, or some other way? Our CLI doc mentions `source-only`, in the UI, it says it's just Source. Does this known  issue apply to the CLI, UI, or both?
created_at: 2025-04-30T09:26:05Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,20 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-29
+
+:_mod-docs-content-type: REFERENCE
+
+[id="known-issues-7-3-0_{context}"]
+= Known issues
+
+This section provides highlighted known issues in {ProductFullName} version 7.3.0.
+
+
+.Application analysis fails to get a list of dependencies for Node.js
+
+When you run an application analysis for the Node.js language provider, the analysis completes with the following error is displayed in the analysis log:
+
+----
+level=error msg="failed to get list of dependencies for provider" error="dependency provider path not set" provider=nodejs'
+----
+
+Currently, there is no workaround available for this issue. (link:https://issues.redhat.com/browse/MTA-5070[MTA-5070])
path: docs/topics/ref_known-issues-7-3-0.adoc
user: login: jortel
body: Being consistent with docs "source-only" is fine.
created_at: 2025-04-30T12:59:38Z
author_association: NONE
diff_hunk: @@ -0,0 +1,20 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-29
+
+:_mod-docs-content-type: REFERENCE
+
+[id="known-issues-7-3-0_{context}"]
+= Known issues
+
+This section provides highlighted known issues in {ProductFullName} version 7.3.0.
+
+
+.Application analysis fails to get a list of dependencies for Node.js
+
+When you run an application analysis for the Node.js language provider, the analysis completes with the following error is displayed in the analysis log:
+
+----
+level=error msg="failed to get list of dependencies for provider" error="dependency provider path not set" provider=nodejs'
+----
+
+Currently, there is no workaround available for this issue. (link:https://issues.redhat.com/browse/MTA-5070[MTA-5070])
path: docs/topics/ref_known-issues-7-3-0.adoc
user: login: mpershina
body: Nice, many thanks! :-)
created_at: 2025-04-30T13:05:12Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,20 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-29
+
+:_mod-docs-content-type: REFERENCE
+
+[id="known-issues-7-3-0_{context}"]
+= Known issues
+
+This section provides highlighted known issues in {ProductFullName} version 7.3.0.
+
+
+.Application analysis fails to get a list of dependencies for Node.js
+
+When you run an application analysis for the Node.js language provider, the analysis completes with the following error is displayed in the analysis log:
+
+----
+level=error msg="failed to get list of dependencies for provider" error="dependency provider path not set" provider=nodejs'
path: docs/topics/ref_known-issues-7-3-0.adoc
user: login: eemcmullan
body: Could be good to note here that the Node provider (also Python provider) does not have a dependency capability. This means a dependency list will not exist, even without this error. 
created_at: 2025-04-30T18:57:06Z
author_association: NONE
diff_hunk: @@ -0,0 +1,20 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-29
+
+:_mod-docs-content-type: REFERENCE
+
+[id="known-issues-7-3-0_{context}"]
+= Known issues
+
+This section provides highlighted known issues in {ProductFullName} version 7.3.0.
+
+
+.Application analysis fails to get a list of dependencies for Node.js
+
+When you run an application analysis for the Node.js language provider, the analysis completes with the following error is displayed in the analysis log:
+
+----
+level=error msg="failed to get list of dependencies for provider" error="dependency provider path not set" provider=nodejs'
+----
+
+To work around this issue, set the `Analysis Mode` setting to `source-only`. (link:https://issues.redhat.com/browse/MTA-5070[MTA-5070])
path: docs/topics/ref_known-issues-7-3-0.adoc
user: login: eemcmullan
body: This step is not necessary for the CLI
created_at: 2025-04-30T18:57:57Z
author_association: NONE
diff_hunk: @@ -0,0 +1,27 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+
+.The deployment manifest generation is now available in {ProductShortName} CLI
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: eemcmullan
body: This is for the asset generation feature
created_at: 2025-04-30T18:58:43Z
author_association: NONE
diff_hunk: @@ -0,0 +1,20 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-29
+
+:_mod-docs-content-type: REFERENCE
+
+[id="known-issues-7-3-0_{context}"]
+= Known issues
+
+This section provides highlighted known issues in {ProductFullName} version 7.3.0.
+
+
+.Application analysis fails to get a list of dependencies for Node.js
+
+When you run an application analysis for the Node.js language provider, the analysis completes with the following error is displayed in the analysis log:
+
+----
+level=error msg="failed to get list of dependencies for provider" error="dependency provider path not set" provider=nodejs'
+----
+
+To work around this issue, set the `Analysis Mode` setting to `source-only`. (link:https://issues.redhat.com/browse/MTA-5070[MTA-5070])
path: docs/topics/ref_known-issues-7-3-0.adoc
user: login: mpershina
body: @eemcmullan, so, this issue exists only in the UI? Or is there some other workaround for the CLI?
created_at: 2025-05-05T12:04:16Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,20 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-29
+
+:_mod-docs-content-type: REFERENCE
+
+[id="known-issues-7-3-0_{context}"]
+= Known issues
+
+This section provides highlighted known issues in {ProductFullName} version 7.3.0.
+
+
+.Application analysis fails to get a list of dependencies for Node.js
+
+When you run an application analysis for the Node.js language provider, the analysis completes with the following error is displayed in the analysis log:
+
+----
+level=error msg="failed to get list of dependencies for provider" error="dependency provider path not set" provider=nodejs'
+----
+
+To work around this issue, set the `Analysis Mode` setting to `source-only`. (link:https://issues.redhat.com/browse/MTA-5070[MTA-5070])
path: docs/topics/ref_known-issues-7-3-0.adoc
user: login: mpershina
body: ```suggestion
To work around this issue, set the `Analysis Mode` setting to `source-only`. 

NOTE: The Node.js provider does not have a dependency capability. Therefore, a dependency list cannot be generated. The same applies for the Python provider.
 
(link:https://issues.redhat.com/browse/MTA-5070[MTA-5070])
```
created_at: 2025-05-05T12:08:34Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,20 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-29
+
+:_mod-docs-content-type: REFERENCE
+
+[id="known-issues-7-3-0_{context}"]
+= Known issues
+
+This section provides highlighted known issues in {ProductFullName} version 7.3.0.
+
+
+.Application analysis fails to get a list of dependencies for Node.js
+
+When you run an application analysis for the Node.js language provider, the analysis completes with the following error is displayed in the analysis log:
+
+----
+level=error msg="failed to get list of dependencies for provider" error="dependency provider path not set" provider=nodejs'
path: docs/topics/ref_known-issues-7-3-0.adoc
user: login: mpershina
body: Added this info as a Note below, could you please check?
created_at: 2025-05-05T12:08:36Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,27 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+
+.The deployment manifest generation is now available in {ProductShortName} CLI
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: mpershina
body: @Pkylas007, please, check if anything needs to be clarified here :-) 
created_at: 2025-05-05T12:09:14Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,27 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+
+.The deployment manifest generation is now available in {ProductShortName} CLI
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: Pkylas007
body: @eemcmullan Can you please clarify if the title must change to:
```suggestion
.Asset generation is now available in {ProductShortName} CLI
```
created_at: 2025-05-05T13:12:43Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,27 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+
+.The deployment manifest generation is now available in {ProductShortName} CLI
+
+Starting with {ProductShortName} {ProductVersion}, you can run the `discover` and `generate` commands in the {CLIName}: 
+
+* The `discover` command generates the discover manifest that preserves the platform and runtime configurations defined in the Cloud Foundry (CF) application manifest.
+* The `generate` command uses the discover manifest to generate the deployment manifest in a Kubernetes-native format to prepare it for {ocp-full} deployments.
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: Pkylas007
body: ```suggestion
* The `generate` command uses the discover manifest to generate the deployment manifest in a Kubernetes-native format to prepare it for {ocp-full} deployments. You can also use the command to generate non-Kubernetes manifests such as a Dockerfile.
```
created_at: 2025-05-05T13:15:10Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,20 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-29
+
+:_mod-docs-content-type: REFERENCE
+
+[id="known-issues-7-3-0_{context}"]
+= Known issues
+
+This section provides highlighted known issues in {ProductFullName} version 7.3.0.
+
+
+.Application analysis fails to get a list of dependencies for Node.js
+
+When you run an application analysis for the Node.js language provider, the analysis completes with the following error is displayed in the analysis log:
+
+----
+level=error msg="failed to get list of dependencies for provider" error="dependency provider path not set" provider=nodejs'
+----
+
+To work around this issue, set the `Analysis Mode` setting to `source-only`. (link:https://issues.redhat.com/browse/MTA-5070[MTA-5070])
path: docs/topics/ref_known-issues-7-3-0.adoc
user: login: eemcmullan
body: The issue is only in the UI
created_at: 2025-05-05T14:47:08Z
author_association: NONE
diff_hunk: @@ -0,0 +1,20 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-29
+
+:_mod-docs-content-type: REFERENCE
+
+[id="known-issues-7-3-0_{context}"]
+= Known issues
+
+This section provides highlighted known issues in {ProductFullName} version 7.3.0.
+
+
+.Application analysis fails to get a list of dependencies for Node.js
+
+When you run an application analysis for the Node.js language provider, the analysis completes with the following error is displayed in the analysis log:
+
+----
+level=error msg="failed to get list of dependencies for provider" error="dependency provider path not set" provider=nodejs'
+----
+
+To work around this issue, set the `Analysis Mode` setting to `source-only`. (link:https://issues.redhat.com/browse/MTA-5070[MTA-5070])
path: docs/topics/ref_known-issues-7-3-0.adoc
user: login: eemcmullan
body: LGTM
created_at: 2025-05-05T14:47:32Z
author_association: NONE
diff_hunk: @@ -0,0 +1,27 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+
+.The deployment manifest generation is now available in {ProductShortName} CLI
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: eemcmullan
body: LGTM
created_at: 2025-05-05T14:50:10Z
author_association: NONE
diff_hunk: @@ -0,0 +1,24 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-29
+
+:_mod-docs-content-type: REFERENCE
+
+[id="known-issues-7-3-0_{context}"]
+= Known issues
+
+This section provides highlighted known issues in {ProductFullName} version 7.3.0.
+
+
+.Application analysis fails to get a list of dependencies for Node.js
+
+When you run an application analysis for the Node.js language provider, the analysis completes with the following error is displayed in the analysis log:
path: docs/topics/ref_known-issues-7-3-0.adoc
user: login: mpershina
body: ```suggestion
.Application analysis fails to get a list of dependencies for Node.js in the {ProductShortName} UI

When you run an application analysis for the Node.js language provider by using the {ProductShortName} user-interface (UI), the analysis completes with the following error is displayed in the analysis log:
```
created_at: 2025-05-05T15:04:54Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,24 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-29
+
+:_mod-docs-content-type: REFERENCE
+
+[id="known-issues-7-3-0_{context}"]
+= Known issues
+
+This section provides highlighted known issues in {ProductFullName} version 7.3.0.
+
+
+.Application analysis fails to get a list of dependencies for Node.js
+
+When you run an application analysis for the Node.js language provider, the analysis completes with the following error is displayed in the analysis log:
path: docs/topics/ref_known-issues-7-3-0.adoc
user: login: mpershina
body: Would this be enough to just mention that the analysis fails only in the UI? This way, the workaround will also apply only to the UI
created_at: 2025-05-05T15:06:11Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,12 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-05-12
+
+:_mod-docs-content-type: REFERENCE
+
+[id="fixed-issues-7-3-0_{context}"]
+= Fixed issues
+
+This section provides the following bug fixes and resolves issues and other problems that have a significant impact on the {ProductFullName} 7.3.0.
+
+
path: docs/topics/ref_fixed-issues-7-3-0.adoc
user: login: Pkylas007
body: @mpershina  can you please include the following fixed issue in 7.3.0 release notes? Dev and QE have approved PR #149 

```suggestion
.MTA CLI now excludes the `target` folder when analyzing compiled Java Maven projects
Previously, for compiled Java Maven projects, the {ProductShortName} CLI included incidents by analyzing the `target` folder. This generated different reports for Java Maven projects before and after running the `mvn-clean-package` command. This issue has been resolved in {ProductShortName} 7.3.0. link:https://issues.redhat.com/browse/MTA-5078[(MTA-5078)]
```
created_at: 2025-05-12T10:28:55Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,24 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-29
+
+:_mod-docs-content-type: REFERENCE
+
+[id="known-issues-7-3-0_{context}"]
+= Known issues
+
+This section provides highlighted known issues in {ProductFullName} version 7.3.0.
+
path: docs/topics/ref_known-issues-7-3-0.adoc
user: login: Pkylas007
body: @mpershina Could you include the following known issue in 7.3 RN, please? Dev and QE have approved PR #151 

```suggestion
.Non-Java applications are analyzed in containerless mode in the {ProductShortName} CLI
When you analyze non-Java applications, {ProductShortName} initiates the analysis in containerless mode. Workaround: set the `--run-local=false` flag to analyze non-Java applications. link:https://issues.redhat.com/browse/MTA-5068[(MTA-5068)]
```
created_at: 2025-05-12T14:55:59Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,12 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-05-12
+
+:_mod-docs-content-type: REFERENCE
+
+[id="fixed-issues-7-3-0_{context}"]
+= Fixed issues
+
+This section provides the following bug fixes and resolves issues and other problems that have a significant impact on the {ProductFullName} 7.3.0.
+
+
+
path: docs/topics/ref_fixed-issues-7-3-0.adoc
user: login: Pkylas007
body: @mpershina Can you please include the following Fixed Issue in 7.3.0? In 7.2.2 PR #152, this is a known issue that has been approved by Dev and QE.

```suggestion

.Application credential update now triggers a new discovery task
Previously, when you update the source or Maven credential for an application, a new discovery task was not triggered in the {ProductShortName} {WebName}. This issue has been resolved in {ProductShortName} 7.3.0. link:https://issues.redhat.com/browse/MTA-5121[(MTA-5121)]
```
created_at: 2025-05-19T02:39:48Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,25 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-29
+
+:_mod-docs-content-type: REFERENCE
+
+[id="known-issues-7-3-0_{context}"]
+= Known issues
+
+This section provides highlighted known issues in {ProductFullName} version 7.3.0.
+.Non-Java applications are analyzed in containerless mode in the {ProductShortName} CLI
path: docs/topics/ref_known-issues-7-3-0.adoc
user: login: mpershina
body: ```suggestion

.Non-Java applications are analyzed in containerless mode in the {ProductShortName} CLI
```
created_at: 2025-05-19T06:12:11Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,26 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-29
+
+:_mod-docs-content-type: REFERENCE
+
+[id="known-issues-7-3-0_{context}"]
+= Known issues
+
path: docs/topics/ref_known-issues-7-3-0.adoc
user: login: Pkylas007
body: @mpershina Please can you add this known issue. It's been approved by dev and QE in #154. Thanks!

```suggestion
.`.NET` Framework application analysis fails in the {ProductShortName} {CLIName} 
When you analyze `.NET` Framework applications in Windows containers using the {ProductShortName} {CLIName}, the analysis fails for the following environment variables: 

* `DOTNET_PROVIDER_IMG`: `quay.io/konveyor/dotnet-external-provider:release-0.7`
* `RUNNER_IMG`: `quay.io/konveyor/kantra:latest`
* `PODMAN_BIN`: `C:\Program Files\Docker\Docker\resources\bin\docker.exe`

Workaround: Use the following version of the Dotnet provider image:
`set DOTNET_PROVIDER_IMG=quay.io/konveyor/dotnet-external-provider:v0.5.0` 
link:https://issues.redhat.com/browse/MTA-5203[(MTA-5203)]
```
created_at: 2025-05-21T12:27:33Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,35 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-29
+
+:_mod-docs-content-type: REFERENCE
+
+[id="known-issues-7-3-0_{context}"]
+= Known issues
+.`.NET` Framework application analysis fails in the {ProductShortName} {CLIName} 
+When you analyze `.NET` Framework applications in Windows containers using the {ProductShortName} {CLIName}, the analysis fails for the following environment variables: 
+
+* `DOTNET_PROVIDER_IMG`: `quay.io/konveyor/dotnet-external-provider:release-0.7`
+* `RUNNER_IMG`: `quay.io/konveyor/kantra:latest`
+* `PODMAN_BIN`: `C:\Program Files\Docker\Docker\resources\bin\docker.exe`
+
+Workaround: Use the following version of the Dotnet provider image:
+`set DOTNET_PROVIDER_IMG=quay.io/konveyor/dotnet-external-provider:v0.5.0` 
+link:https://issues.redhat.com/browse/MTA-5203[(MTA-5203)]
+This section provides highlighted known issues in {ProductFullName} version 7.3.0.
path: docs/topics/ref_known-issues-7-3-0.adoc
user: login: mpershina
body: ```suggestion

```
created_at: 2025-05-22T07:10:53Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,35 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-29
+
+:_mod-docs-content-type: REFERENCE
+
+[id="known-issues-7-3-0_{context}"]
+= Known issues
+.`.NET` Framework application analysis fails in the {ProductShortName} {CLIName} 
path: docs/topics/ref_known-issues-7-3-0.adoc
user: login: mpershina
body: ```suggestion

This section provides highlighted known issues in {ProductFullName} version 7.3.0.

.`.NET` Framework application analysis fails in the {ProductShortName} {CLIName} 
```
created_at: 2025-05-22T07:11:07Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,37 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-29
+
+:_mod-docs-content-type: REFERENCE
+
+[id="known-issues-7-3-0_{context}"]
+= Known issues
+
+This section provides highlighted known issues in {ProductFullName} version 7.3.0.
+
+.`.NET` Framework application analysis fails in the {ProductShortName} {CLIName} 
+When you analyze `.NET` Framework applications in Windows containers using the {ProductShortName} {CLIName}, the analysis fails for the following environment variables: 
+
+* `DOTNET_PROVIDER_IMG`: `quay.io/konveyor/dotnet-external-provider:release-0.7`
+* `RUNNER_IMG`: `quay.io/konveyor/kantra:latest`
+* `PODMAN_BIN`: `C:\Program Files\Docker\Docker\resources\bin\docker.exe`
+
+Workaround: Use the following version of the Dotnet provider image:
+`set DOTNET_PROVIDER_IMG=quay.io/konveyor/dotnet-external-provider:v0.5.0` 
+link:https://issues.redhat.com/browse/MTA-5203[(MTA-5203)]
+
+.Non-Java applications are analyzed in containerless mode in the {ProductShortName} CLI
+When you analyze non-Java applications, {ProductShortName} initiates the analysis in containerless mode. Workaround: set the `--run-local=false` flag to analyze non-Java applications. link:https://issues.redhat.com/browse/MTA-5068[(MTA-5068)]
+
+.Application analysis fails to get a list of dependencies for Node.js in the {ProductShortName} UI
+
+When you run an application analysis for the Node.js language provider by using the {ProductShortName} user-interface (UI), the analysis completes with the following error is displayed in the analysis log:
+
+----
+level=error msg="failed to get list of dependencies for provider" error="dependency provider path not set" provider=nodejs'
+----
+
+To work around this issue, set the `Analysis Mode` setting to `source-only`. 
path: docs/topics/ref_known-issues-7-3-0.adoc
user: login: mpershina
body: ```suggestion
Workaround: Set the `Analysis Mode` setting to `source-only`. 
```
created_at: 2025-05-22T07:12:00Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,27 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+
+.Asset generation is now available in {ProductShortName} CLI
+
+Starting with {ProductShortName} {ProductVersion}, you can run the `discover` and `generate` commands in the {CLIName}: 
+
+* The `discover` command generates the discover manifest that preserves the platform and runtime configurations defined in the Cloud Foundry (CF) application manifest.
+* The `generate` command uses the discover manifest to generate the deployment manifest in a Kubernetes-native format to prepare it for {ocp-full} deployments. You can also use the command to generate non-Kubernetes manifests such as a Dockerfile.
+
+(link:https://issues.redhat.com/browse/MTA-4610[MTA-4610])
+
+.{ProductShortName} now uses Red Hat Build of Keycloak for user authentication
+
+{ProductShortName} {ProductVersion} now uses `{rhbk-first}` instance for user authentication and authorization. The {ProductShortName} Operator manages the `{rhbk-short}` instance and configures a dedicated realm with necessary roles and permissions. For `{rhbk-short}`, the secret and the pod name has changed. The pod name for {rhbk-short} is changed to `rhbk-operator`. (link:https://issues.redhat.com/browse/MTA-4540[MTA-4540])
+
+.Listing all languages in an application is now supported
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: mpershina
body: @Pkylas007, could you please add the ticket number to this RN? 
Thanks :-) 
created_at: 2025-05-22T07:15:09Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,27 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+
+.Asset generation is now available in {ProductShortName} CLI
+
+Starting with {ProductShortName} {ProductVersion}, you can run the `discover` and `generate` commands in the {CLIName}: 
+
+* The `discover` command generates the discover manifest that preserves the platform and runtime configurations defined in the Cloud Foundry (CF) application manifest.
+* The `generate` command uses the discover manifest to generate the deployment manifest in a Kubernetes-native format to prepare it for {ocp-full} deployments. You can also use the command to generate non-Kubernetes manifests such as a Dockerfile.
+
+(link:https://issues.redhat.com/browse/MTA-4610[MTA-4610])
+
+.{ProductShortName} now uses Red Hat Build of Keycloak for user authentication
+
+{ProductShortName} {ProductVersion} now uses `{rhbk-first}` instance for user authentication and authorization. The {ProductShortName} Operator manages the `{rhbk-short}` instance and configures a dedicated realm with necessary roles and permissions. For `{rhbk-short}`, the secret and the pod name has changed. The pod name for {rhbk-short} is changed to `rhbk-operator`. (link:https://issues.redhat.com/browse/MTA-4540[MTA-4540])
+
+.Listing all languages in an application is now supported
+
+In {ProductShortName} {ProductVersion}, you can list all languages in an application by using the `--list-languages` flag in the {CLIName}. The listed language that has no supported providers requires a custom rule set and the --`override-provider-settings` flag when you analyze the application.
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: Pkylas007
body: ```suggestion
In {ProductShortName} {ProductVersion}, you can list all languages in an application by using the `--list-languages` flag in the {CLIName}. The listed language that has no supported providers requires a custom rule set and the --`override-provider-settings` flag when you analyze the application. (link:https://issues.redhat.com/browse/MTA-4798[MTA-4798])
```
created_at: 2025-05-22T07:18:28Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,27 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+
+.Asset generation is now available in {ProductShortName} CLI
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: istein1
body: Asset Generation is DEV preview
created_at: 2025-05-22T08:43:56Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,27 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+
+.Asset generation is now available in {ProductShortName} CLI
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: Pkylas007
body: ```suggestion
.Asset generation is available as a Developer Preview in {ProductShortName} CLI
```
created_at: 2025-05-22T09:16:34Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,27 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2025-04-17
+
+:_mod-docs-content-type: REFERENCE
+
+[id="new-features-7-3-0_{context}"]
+= New features
+
+This section provides the new features and improvements of the {ProductFullName} 7.3.0. 
+
+
+.Asset generation is now available in {ProductShortName} CLI
+
+Starting with {ProductShortName} {ProductVersion}, you can run the `discover` and `generate` commands in the {CLIName}: 
+
+* The `discover` command generates the discover manifest that preserves the platform and runtime configurations defined in the Cloud Foundry (CF) application manifest.
+* The `generate` command uses the discover manifest to generate the deployment manifest in a Kubernetes-native format to prepare it for {ocp-full} deployments. You can also use the command to generate non-Kubernetes manifests such as a Dockerfile.
+
+(link:https://issues.redhat.com/browse/MTA-4610[MTA-4610])
+
+.{ProductShortName} now uses Red Hat Build of Keycloak for user authentication
+
+{ProductShortName} {ProductVersion} now uses `{rhbk-first}` instance for user authentication and authorization. The {ProductShortName} Operator manages the `{rhbk-short}` instance and configures a dedicated realm with necessary roles and permissions. For `{rhbk-short}`, the secret and the pod name has changed. The pod name for {rhbk-short} is changed to `rhbk-operator`. (link:https://issues.redhat.com/browse/MTA-4540[MTA-4540])
+
+.Listing all languages in an application is now supported
path: docs/topics/ref_new-features-7-3-0.adoc
user: login: Pkylas007
body: ```suggestion
.Listing all languages in an application is available as a Developer Preview
```
created_at: 2025-05-22T09:17:45Z
author_association: COLLABORATOR
diff_hunk: @@ -18,4 +18,25 @@ When you analyze `.NET` Framework applications in Windows containers using the {
 
 Workaround: Use the following version of the Dotnet provider image:
 `set DOTNET_PROVIDER_IMG=quay.io/konveyor/dotnet-external-provider:v0.5.0` 
-link:https://issues.redhat.com/browse/MTA-5203[(MTA-5203)]
\ No newline at end of file
+
+link:https://issues.redhat.com/browse/MTA-5203[(MTA-5203)]
+
+.Non-Java applications are analyzed in containerless mode in the {ProductShortName} CLI
+When you analyze non-Java applications, {ProductShortName} initiates the analysis in containerless mode. 
+
+Workaround: set the `--run-local=false` flag to analyze non-Java applications. link:https://issues.redhat.com/browse/MTA-5068[(MTA-5068)]
+
+
+.Application analysis fails to get a list of dependencies for Node.js in the {ProductShortName} UI
+
+When you run an application analysis for the Node.js language provider by using the {ProductShortName} user-interface (UI), the analysis completes with the following error is displayed in the analysis log:
path: docs/topics/ref_known-issues-7-3-0.adoc
user: login: abrugaro
body: ```suggestion
When you run an application analysis for the Node.js language provider by using the {ProductShortName} user-interface (UI), the analysis completes with the following error displayed in the analysis log:
```
created_at: 2025-05-22T09:52:32Z
author_association: NONE
diff_hunk: @@ -18,4 +18,25 @@ When you analyze `.NET` Framework applications in Windows containers using the {
 
 Workaround: Use the following version of the Dotnet provider image:
 `set DOTNET_PROVIDER_IMG=quay.io/konveyor/dotnet-external-provider:v0.5.0` 
-link:https://issues.redhat.com/browse/MTA-5203[(MTA-5203)]
\ No newline at end of file
+
+link:https://issues.redhat.com/browse/MTA-5203[(MTA-5203)]
+
+.Non-Java applications are analyzed in containerless mode in the {ProductShortName} CLI
+When you analyze non-Java applications, {ProductShortName} initiates the analysis in containerless mode. 
+
+Workaround: set the `--run-local=false` flag to analyze non-Java applications. link:https://issues.redhat.com/browse/MTA-5068[(MTA-5068)]
+
+
+.Application analysis fails to get a list of dependencies for Node.js in the {ProductShortName} UI
+
+When you run an application analysis for the Node.js language provider by using the {ProductShortName} user-interface (UI), the analysis completes with the following error is displayed in the analysis log:
path: docs/topics/ref_known-issues-7-3-0.adoc
user: login: mpershina
body: Ah, it's just a sentence structure thing :-)  We can either rephrase it to use "is" or leave it as it is.
created_at: 2025-05-22T10:02:37Z
author_association: COLLABORATOR

PR comments:
user: login: mpershina
created_at: 2025-05-22T07:35:51Z
body: Hi @rromannissen, @istein1, @abrugaro, @eemcmullan, could you please review this whole Release notes PR? 
 Let me know if you also want the preview.
Thanks :-)
author_association: COLLABORATOR
user: login: mpershina
created_at: 2025-05-22T10:04:17Z
body: @istein1, I've added the Dev preview admonitions to both RNs. Is everything ok now? 
If yes, could you please approve the PR?
Thanks!
author_association: COLLABORATOR
user: login: istein1
created_at: 2025-05-22T10:20:59Z
body: LGTM
author_association: MEMBER