Jun 29, 2023 · Jun 26, 2023 · Jun 26, 2023 · Jun 27, 2023 · Jun 27, 2023 · Jun 27, 2023
diff --git a/_docs/dashboards/home-dashboard.md b/_docs/dashboards/home-dashboard.md
 | --------------   | --------------|
 | **Date Range** | The time frame for which to view data. The date range affects the other filters, including the granularity for the Success Rate and Pipeline Duration charts. <br>In addition to the predefined date ranges, you can select a custom date range of up to the last six months. <br>If you select Today, then the Success Rate and Duration charts reflect hourly granularity.<br><br>Every date range you select has a reference period corresponding to the same period of time preceding the selected date range. The reference period is used to derive comparisons and identify trends.  |
 | **Hourly/Daily** |Based on the date range selected, choose the granularity for viewing Success Rate and Pipeline Duration. {::nomarkdown}<ul><li>A date range between 1 and 4 days allows viewing metrics either by hour or by day.</li><li>A date range longer than four days allows viewing metrics only by day. The Hourly option is disabled in this case.</li></ul> {:/}
 | **Project**           | The project or projects to which the pipeline belongs. Selecting a project allows you to focus on performance of pipelines assigned to it. If you starred one or more projects as favorites, clicking {::nomarkdown}<img src="../../../images/icons/icon-fav-starred.png?display=inline-block">{:/}, filters pipelines by the selected projects.|
 | **Pipeline**           | The pipeline or pipelines to filter by. <br>If you starred one or more pipelines as favorites, clicking {::nomarkdown}<img src="../../../images/icons/icon-fav-starred.png?display=inline-block">{:/}, filters by those pipelines. |
 | **Project**           | The project or projects to which the pipeline belongs. Selecting a project allows you to focus on performance of pipelines assigned to it. If you starred one or more projects as favorites and selected projects, clicking {::nomarkdown}<img src="../../../images/icons/icon-fav-starred.png?display=inline-block">{:/}, filters pipelines by the selected projects.|
 | **Pipeline**           | The pipeline or pipelines to filter by. <br>Mouse over a pipeline name in the list displays a tooltip including the name of the project to which the pipeline belongs, followed by the name of the pipeline, to easily identify and select the correct pipeline.<br>If you starred one or more pipelines as favorites, clicking {::nomarkdown}<img src="../../../images/icons/icon-fav-starred.png?display=inline-block">{:/}, filters by those pipelines. |
 | **Status**           | {::nomarkdown}<ul><li><b>Error</b>: Pipelines with builds that failed due to errors in the pipeline specifications or steps that failed. </li><li><b>Succeeded</b>: Pipelines with builds that completed successfully.</li> <li><b>Terminated</b>: Pipelines with builds terminated by the system according to the policy defined in the pipeline's settings. These can be any of these: <ul><li>Recent build from the same branch terminating all previous pipeline builds </li><li>Recent build from the specified branch terminating all previous builds from that branch</li><li>Running build terminating all running builds</li><li>Child builds terminated when the parent build is terminated.</li> </ul></li>For details, see <a href ="https://codefresh.io/docs/docs/pipelines/pipelines/#policies">Build Termination in Pipeline Policies</a>. </ul>{:/}|
 | **Tags**             |The tag or tags assigned to the pipelines. |
 |{::nomarkdown}<img src="../../../images/icons/icon-mark-favorite.png?display=inline-block">{:/}| Filter to view only projects or pipelines that have been starred as favorites in the [Projects/Pipeline pages]({{site.baseurl}}/docs/pipelines/monitoring-pipelines/#starring-projects-and-pipelines-as-favorites).<br><br>When you have starred projects or pipelines, the icon changes to {::nomarkdown}<img src="../../../images/icons/icon-fav-starred.png?display=inline-block">.<br>Clicking it filters by favorite projects and pipelines. {:/} |
diff --git a/_docs/getting-started/command-bar.md b/_docs/getting-started/command-bar.md


 ## Find actions & configuration settings
 In addition to quickly navigating to specific entities such asBuilds and Pipelines, administrators can navigate to configuration settingssuch as Single Sign-On, and installation actions.
 In addition to quickly navigating to specific entities such asProjects and Pipelines, administrators can navigate to configuration settingsfor Single Sign-On, and installation actions.

 {% include
 image.html
diff --git a/_docs/whats-new/on-prem-release-notes.md b/_docs/whats-new/on-prem-release-notes.md
 #### Pipelines Dashboard
 This release introduces the much-awaited Pipelines Dashboard!  The dashboard, dedicated to pipelines and pipeline metrics, is a new experience of pipeline visibility and monitoring.
 Clicking Home Dashboard located at the top of the sidebar displays the Pipelines Dashboard.
 If you're currently using both GitOps and Pipelines, the Pipelines Dashboard is displayed afterthe GitOps and Argo Workflow dashboards..
 If you're currently using both GitOps and Pipelines, the Pipelines Dashboard is displayedbelowthe GitOps and Argo Workflow dashboards.

 Use the Pipelines dashboard to:
 * Identify pipelines with low performance, both in terms of number of executions and execution duration
diff --git a/_posts/2023-06-29-june-release-notes.md b/_posts/2023-06-29-june-release-notes.md
 ---
 title: "Release Notes: June 2023"
 description: "Release Notes for Codefresh Pipelines and GitOps"
 ---

 ## Features & enhancements


 ### Global Search & Navigation
 Boost your Codefresh experience with our latest feature, Global Search & Navigation! Be it navigation, actions such as switching accounts, or finding entities such as projects or pipelines, Global Search & Navigation lets you get to what and where you need without extra clicks.

 {% include
 image.html
 lightbox="true"
 file="/images/whats-new/june23/rel-notes-june23-command-bar.png"
 url="/images/whats-new/june23/rel-notes-june23-command-bar.png"
 alt="Global Search & Navigation in Codefresh"
 caption="Global Search & Navigation in Codefresh"
 max-width="60%"
 %}

 **Search & find**
 With Global Search & Navigation, you can easily monitor and find resources in your projects and pipelines, with frequently used entities organized into categories for quick search. Easily find a specific project, or pipeline, or browse them all.
 We’ll be adding applications to our entity list, so stay tuned for the announcement.

 In addition, Global Search & Navigation pulls up links to relevant information from our documentation that may be useful within your current context, making it even easier to find what you need.

 **Switch accounts**
 Global Search & Navigation allows you to switch accounts without needing to navigate to your avatar drop-down menu in the toolbar. Simply search for the account, select the Switch Account action, and then choose the account you wish to switch to.

 **Keyboard shortcuts**
 We have also added keyboard shortcuts to save time and get things done even faster. You can quickly bring up Global Search & Navigation, and get to the entities you need in Projects and Pipelines.


 For details, see [Global Search & Navigation]({{site.baseurl}}/docs/getting-started/command-bar/).


 ### Gerrit as Git provider for Pipelines and GitOps
 We are excited to announce the integration of Gerrit, the open-source web-based code review tool for Git repositories, with Codefresh.

 **Gerrit and Codefresh Pipelines**
 By integrating Gerrit as a Git provider for Codefresh Pipelines, you can leverage its capabilities to trigger builds and tests automatically whenever a new change is pushed to Git repositories hosted in Gerrit. The integration allows you to closely monitor the status of builds and tests within the Gerrit environment itself, providing you with a comprehensive view of your development process.
 With Codefresh’s `CF_PULL_REQUEST` group of environment variables, you can achieve similar functionality to Gerrit’s `Changes` directly within Codefresh.

 For details, see [Pipeline integrations - Git providers]({{site.baseurl}}/docs/integrations/git-providers/#gerrit).

 **Gerrit and Codefresh GitOps**
 By configuring Gerrit as the primary Git provider for your Hosted GitOps Runtime, you can integrate Gerrit information into your third-party CI tools or platforms for image enrichment and reporting in Codefresh.
 If you are interested in using Gerrit for Hybrid GitOps Runtimes, please contact us.

 For details, see [GitOps Gerrit Git provider integration]({{site.baseurl}}/docs/gitops-integrations/gerrit-integration/).

 ### Pipelines: Pipeline Dashboard enhancements
 Review the latest enhancements in the Pipelines Dashboard.

 {% include
 image.html
 lightbox="true"
 file="/images/whats-new/june23/rel-notes-june23-pipeline-dashboard-updates.png"
 url="/images/whats-new/june23/rel-notes-june23-pipeline-dashboard-updates.png"
 alt="Favorites filter and Last Update in Pipelines Dashboard"
 caption="Favorites filter and Last Update in Pipelines Dashboard"
 max-width="60%"
 %}

 **Filter by favorite pipelines**
 The Pipelines Dashboard now has a Favorites filter. If you starred any projects or pipelines as favorites, you can easily view your favorite pipelines, both by projects or individual pipelines.

 **Recent update indication**
 The Last Update timestamp on the top right of the Pipelines Dashboard, refreshes automatically to show you the exact time the data was retrieved.

 **Full path display for pipelines in filter**
 Previously, in the Pipelines filter, it was challenging to identify the correct pipeline, when multiple pipelines shared the same name across different projects.
 Now, when you mouse over a pipeline name in the list, the tooltip displays the full path, including the name of the project to which the pipeline belongs, followed by the name of the pipeline. With this update, you can easily identify and select the correct pipeline in the Pipelines filter, even when multiple pipelines share the same name across different projects.

 For details, see [Pipelines Dashboard]({{site.baseurl}}/docs/dashboards/home-dashboard/#pipelines-dashboard).

 ### Pipelines: New icons for pipeline build statuses
 Pipeline builds have new status icons. With distinct icons for each status, you can easily differentiate between builds, bringing clarity and saving time. Previously, both terminated and failed builds had the same icon for example, causing confusion.

 Here are the icons and the build statuses they represent:
 * **Running**: {::nomarkdown}<img src="../../../../../images/whats-new/june23/pipeline-build-running.png" display=inline-block/> {:/}
 * **Completed**: {::nomarkdown}<img src="../../../../../images/whats-new/june23/pipeline-build-successful.png" display=inline-block/> {:/}
 * **Delayed**: {::nomarkdown}<img src="../../../../../images/whats-new/june23/pipeline-build-delayed.png" display=inline-block/> {:/}
 * **Pending approval**: {::nomarkdown}<img src="../../../../../images/whats-new/june23/pipeline-build-pending-approval.png" display=inline-block/> {:/}
 * **Denied approval**: {::nomarkdown}<img src="../../../../../images/whats-new/june23/pipeline-build-denied.png" display=inline-block/> {:/}
 * **Terminating**: {::nomarkdown}<img src="../../../../../images/whats-new/june23/pipeline-build-terminating.png" display=inline-block/> {:/}
 * **Terminated**: {::nomarkdown}<img src="../../../../../images/whats-new/june23/pipeline-build-terminated.png" display=inline-block/> {:/}
 * **Failed**: {::nomarkdown}<img src="../../../../../images/whats-new/june23/pipeline-build-failed-error.png" display=inline-block/> {:/}

 For details, see [Viewing status for pipeline builds]({{site.baseurl}}/docs/pipelines/monitoring-pipelines/#viewing-status-for-pipeline-builds).

 ### GitOps: Helm-based Hybrid Runtimes
 As part of our ongoing commitment to improving efficiency and simplifying installations, we have transitioned from the previous CLI-based installation method to native Kubernetes installation using Helm charts. This change simplifies the installation process and aligns with industry-standard practices for Kubernetes deployments.

 **Helm installation for Hybrid GitOps**
  Moving forward, we are deprecating the CLI-based installation method for Hybrid GitOps Runtimes. Helm provides better control and ensures compatibility, enabling you to seamlessly manage GitOps Runtimes deployments across various clusters.
  For details, see [Hybrid GitOps Runtime installation]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops-helm-installation/).

 <!---
 * On-Premises version of Codefresh GitOps Runtime
  We also introduced an on-premises version of the GitOps Runtime, allowing you to deploy and manage your Codefresh infrastructure within your private network.
  The on-premises version gives you greater control over your environment, ensuring data security and compliance while leveraging the powerful features and integrations of Codefresh GitOps and Argo CD.
  For details, see [On-premises GitOps Runtime installation]({{site.baseurl}}/docs/installation/gitops/on-prem-gitops-runtime-install/).
 -->

 ## Bug fixes
 **General**
 * Unable to add users to Codefresh via team sync for Okta.


 **Pipelines**
 * Pipeline builds terminate with error message: `Pipeline could not be executed because retry attempts limit has been exceeded...`.
 * Discrepancy in list of builds returned when running `GET {{baseUrl/workflow?pipeline=[pipeline-id]}}` query.
 * Shallow clone for a specific revision with `depth` argument results in error: `pathspec 'test' did not match any file(s) known to git`.
 * Composition stops randomly with error: `Could not get status for container <container-name>`.
 * Unable to define CRON triggers for pipelines.
 * Cross-account ECR pull in `freestyle` step fails with `(HTTP code 500) server error...`.
 * In the Builds page, steps are grayed out, and the Output tab for a step displays `loading` instead of the step logs.
 * Creating a Git trigger for a repo name containing spaces fails with error: `Failed to create trigger...fails to match the required pattern...`.
 * Unable to set `requiredAvailableStorage` programmatically for Hybrid Pipeline Runtimes.
 * 404 errors on clicking documentation links in Build > Triggers.

 **GitOps**
 * Unable to delete Argo CD application from Git Source.
 * Same application shows different statuses in the **Home > GitOps Dashboard** and in the **GitOps Apps** dashboard.
 * Images not displayed in Images dashboard for GitLab Git provider (Denis)
 * (On premises) Rollouts Reporter for managed cluster uses SaaS instead of on-premises URL.




diff --git a/images/administration/command-bar/quick-search-options.png b/images/administration/command-bar/quick-search-options.png
diff --git a/images/pipeline/dashboard/pipeline-dashboard.png b/images/pipeline/dashboard/pipeline-dashboard.png
diff --git a/images/whats-new/june23/pipeline-build-delayed.png b/images/whats-new/june23/pipeline-build-delayed.png
diff --git a/images/whats-new/june23/pipeline-build-denied.png b/images/whats-new/june23/pipeline-build-denied.png
diff --git a/images/whats-new/june23/pipeline-build-failed-error.png b/images/whats-new/june23/pipeline-build-failed-error.png
diff --git a/images/whats-new/june23/pipeline-build-pending-approval.png b/images/whats-new/june23/pipeline-build-pending-approval.png
diff --git a/images/whats-new/june23/pipeline-build-running.png b/images/whats-new/june23/pipeline-build-running.png
diff --git a/images/whats-new/june23/pipeline-build-successful.png b/images/whats-new/june23/pipeline-build-successful.png
diff --git a/images/whats-new/june23/pipeline-build-terminated.png b/images/whats-new/june23/pipeline-build-terminated.png
diff --git a/images/whats-new/june23/pipeline-build-terminating.png b/images/whats-new/june23/pipeline-build-terminating.png
diff --git a/images/whats-new/june23/rel-notes-june23-command-bar.png b/images/whats-new/june23/rel-notes-june23-command-bar.png
diff --git a/images/whats-new/june23/rel-notes-june23-gerrit-pipelines.png b/images/whats-new/june23/rel-notes-june23-gerrit-pipelines.png
diff --git a/images/whats-new/june23/rel-notes-june23-pipeline-dashboard-updates.png b/images/whats-new/june23/rel-notes-june23-pipeline-dashboard-updates.png
Original file line number	Diff line number	Diff line change
Expand Up		@@ -264,8 +264,8 @@ Different filter types have an AND relationship.
		\| -------------- \| --------------\|
		\| Date Range \| The time frame for which to view data. The date range affects the other filters, including the granularity for the Success Rate and Pipeline Duration charts. <br>In addition to the predefined date ranges, you can select a custom date range of up to the last six months. <br>If you select Today, then the Success Rate and Duration charts reflect hourly granularity.<br><br>Every date range you select has a reference period corresponding to the same period of time preceding the selected date range. The reference period is used to derive comparisons and identify trends. \|
		\| Hourly/Daily \|Based on the date range selected, choose the granularity for viewing Success Rate and Pipeline Duration. {::nomarkdown}<ul><li>A date range between 1 and 4 days allows viewing metrics either by hour or by day.</li><li>A date range longer than four days allows viewing metrics only by day. The Hourly option is disabled in this case.</li></ul> {:/}
		\| Project \| The project or projects to which the pipeline belongs. Selecting a project allows you to focus on performance of pipelines assigned to it. If you starred one or more projects as favorites, clicking {::nomarkdown}<img src="../../../images/icons/icon-fav-starred.png?display=inline-block">{:/}, filters pipelines by the selected projects.\|
		\| Pipeline \| The pipeline or pipelines to filter by. <br>If you starred one or more pipelines as favorites, clicking {::nomarkdown}<img src="../../../images/icons/icon-fav-starred.png?display=inline-block">{:/}, filters by those pipelines. \|
		\| Project \| The project or projects to which the pipeline belongs. Selecting a project allows you to focus on performance of pipelines assigned to it. If you starred one or more projects as favorites and selected projects, clicking {::nomarkdown}<img src="../../../images/icons/icon-fav-starred.png?display=inline-block">{:/}, filters pipelines by the selected projects.\|
		\| Pipeline \| The pipeline or pipelines to filter by. <br>Mouse over a pipeline name in the list displays a tooltip including the name of the project to which the pipeline belongs, followed by the name of the pipeline, to easily identify and select the correct pipeline.<br>If you starred one or more pipelines as favorites, clicking {::nomarkdown}<img src="../../../images/icons/icon-fav-starred.png?display=inline-block">{:/}, filters by those pipelines. \|
		\| Status \| {::nomarkdown}<ul><li><b>Error</b>: Pipelines with builds that failed due to errors in the pipeline specifications or steps that failed. </li><li><b>Succeeded</b>: Pipelines with builds that completed successfully.</li> <li><b>Terminated</b>: Pipelines with builds terminated by the system according to the policy defined in the pipeline's settings. These can be any of these: <ul><li>Recent build from the same branch terminating all previous pipeline builds </li><li>Recent build from the specified branch terminating all previous builds from that branch</li><li>Running build terminating all running builds</li><li>Child builds terminated when the parent build is terminated.</li> </ul></li>For details, see <a href ="https://codefresh.io/docs/docs/pipelines/pipelines/#policies">Build Termination in Pipeline Policies</a>. </ul>{:/}\|
		\| Tags \|The tag or tags assigned to the pipelines. \|
		\|{::nomarkdown}<img src="../../../images/icons/icon-mark-favorite.png?display=inline-block">{:/}\| Filter to view only projects or pipelines that have been starred as favorites in the [Projects/Pipeline pages]({{site.baseurl}}/docs/pipelines/monitoring-pipelines/#starring-projects-and-pipelines-as-favorites).<br><br>When you have starred projects or pipelines, the icon changes to {::nomarkdown}<img src="../../../images/icons/icon-fav-starred.png?display=inline-block">.<br>Clicking it filters by favorite projects and pipelines. {:/} \|
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -63,7 +63,7 @@ Here are a few keyboard shortcuts to work with Global Search & Navigation.


		## Find actions & configuration settings
		In addition to quickly navigating to specific entities such asBuilds and Pipelines, administrators can navigate to configuration settingssuch as Single Sign-On, and installation actions.
		In addition to quickly navigating to specific entities such asProjects and Pipelines, administrators can navigate to configuration settingsfor Single Sign-On, and installation actions.

		{% include
		image.html
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -71,7 +71,7 @@ We are always adding more options, so stay tuned for announcements.
		#### Pipelines Dashboard
		This release introduces the much-awaited Pipelines Dashboard! The dashboard, dedicated to pipelines and pipeline metrics, is a new experience of pipeline visibility and monitoring.
		Clicking Home Dashboard located at the top of the sidebar displays the Pipelines Dashboard.
		If you're currently using both GitOps and Pipelines, the Pipelines Dashboard is displayed afterthe GitOps and Argo Workflow dashboards..
		If you're currently using both GitOps and Pipelines, the Pipelines Dashboard is displayedbelowthe GitOps and Argo Workflow dashboards.

		Use the Pipelines dashboard to:
		* Identify pipelines with low performance, both in terms of number of executions and execution duration
Expand Down
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1,132 @@
		---
		title: "Release Notes: June 2023"
		description: "Release Notes for Codefresh Pipelines and GitOps"
		---

		## Features & enhancements


		### Global Search & Navigation
		Boost your Codefresh experience with our latest feature, Global Search & Navigation! Be it navigation, actions such as switching accounts, or finding entities such as projects or pipelines, Global Search & Navigation lets you get to what and where you need without extra clicks.

		{% include
		image.html
		lightbox="true"
		file="/images/whats-new/june23/rel-notes-june23-command-bar.png"
		url="/images/whats-new/june23/rel-notes-june23-command-bar.png"
		alt="Global Search & Navigation in Codefresh"
		caption="Global Search & Navigation in Codefresh"
		max-width="60%"
		%}

		Search & find
		With Global Search & Navigation, you can easily monitor and find resources in your projects and pipelines, with frequently used entities organized into categories for quick search. Easily find a specific project, or pipeline, or browse them all.
		We’ll be adding applications to our entity list, so stay tuned for the announcement.

		In addition, Global Search & Navigation pulls up links to relevant information from our documentation that may be useful within your current context, making it even easier to find what you need.

		Switch accounts
		Global Search & Navigation allows you to switch accounts without needing to navigate to your avatar drop-down menu in the toolbar. Simply search for the account, select the Switch Account action, and then choose the account you wish to switch to.

		Keyboard shortcuts
		We have also added keyboard shortcuts to save time and get things done even faster. You can quickly bring up Global Search & Navigation, and get to the entities you need in Projects and Pipelines.


		For details, see [Global Search & Navigation]({{site.baseurl}}/docs/getting-started/command-bar/).


		### Gerrit as Git provider for Pipelines and GitOps
		We are excited to announce the integration of Gerrit, the open-source web-based code review tool for Git repositories, with Codefresh.

		Gerrit and Codefresh Pipelines
		By integrating Gerrit as a Git provider for Codefresh Pipelines, you can leverage its capabilities to trigger builds and tests automatically whenever a new change is pushed to Git repositories hosted in Gerrit. The integration allows you to closely monitor the status of builds and tests within the Gerrit environment itself, providing you with a comprehensive view of your development process.
		With Codefresh’s `CF_PULL_REQUEST` group of environment variables, you can achieve similar functionality to Gerrit’s `Changes` directly within Codefresh.

		For details, see [Pipeline integrations - Git providers]({{site.baseurl}}/docs/integrations/git-providers/#gerrit).

		Gerrit and Codefresh GitOps
		By configuring Gerrit as the primary Git provider for your Hosted GitOps Runtime, you can integrate Gerrit information into your third-party CI tools or platforms for image enrichment and reporting in Codefresh.
		If you are interested in using Gerrit for Hybrid GitOps Runtimes, please contact us.

		For details, see [GitOps Gerrit Git provider integration]({{site.baseurl}}/docs/gitops-integrations/gerrit-integration/).

		### Pipelines: Pipeline Dashboard enhancements
		Review the latest enhancements in the Pipelines Dashboard.

		{% include
		image.html
		lightbox="true"
		file="/images/whats-new/june23/rel-notes-june23-pipeline-dashboard-updates.png"
		url="/images/whats-new/june23/rel-notes-june23-pipeline-dashboard-updates.png"
		alt="Favorites filter and Last Update in Pipelines Dashboard"
		caption="Favorites filter and Last Update in Pipelines Dashboard"
		max-width="60%"
		%}

		Filter by favorite pipelines
		The Pipelines Dashboard now has a Favorites filter. If you starred any projects or pipelines as favorites, you can easily view your favorite pipelines, both by projects or individual pipelines.

		Recent update indication
		The Last Update timestamp on the top right of the Pipelines Dashboard, refreshes automatically to show you the exact time the data was retrieved.

		Full path display for pipelines in filter
		Previously, in the Pipelines filter, it was challenging to identify the correct pipeline, when multiple pipelines shared the same name across different projects.
		Now, when you mouse over a pipeline name in the list, the tooltip displays the full path, including the name of the project to which the pipeline belongs, followed by the name of the pipeline. With this update, you can easily identify and select the correct pipeline in the Pipelines filter, even when multiple pipelines share the same name across different projects.

		For details, see [Pipelines Dashboard]({{site.baseurl}}/docs/dashboards/home-dashboard/#pipelines-dashboard).

		### Pipelines: New icons for pipeline build statuses
		Pipeline builds have new status icons. With distinct icons for each status, you can easily differentiate between builds, bringing clarity and saving time. Previously, both terminated and failed builds had the same icon for example, causing confusion.

		Here are the icons and the build statuses they represent:
		* Running: {::nomarkdown}<img src="../../../../../images/whats-new/june23/pipeline-build-running.png" display=inline-block/> {:/}
		* Completed: {::nomarkdown}<img src="../../../../../images/whats-new/june23/pipeline-build-successful.png" display=inline-block/> {:/}
		* Delayed: {::nomarkdown}<img src="../../../../../images/whats-new/june23/pipeline-build-delayed.png" display=inline-block/> {:/}
		* Pending approval: {::nomarkdown}<img src="../../../../../images/whats-new/june23/pipeline-build-pending-approval.png" display=inline-block/> {:/}
		* Denied approval: {::nomarkdown}<img src="../../../../../images/whats-new/june23/pipeline-build-denied.png" display=inline-block/> {:/}
		* Terminating: {::nomarkdown}<img src="../../../../../images/whats-new/june23/pipeline-build-terminating.png" display=inline-block/> {:/}
		* Terminated: {::nomarkdown}<img src="../../../../../images/whats-new/june23/pipeline-build-terminated.png" display=inline-block/> {:/}
		* Failed: {::nomarkdown}<img src="../../../../../images/whats-new/june23/pipeline-build-failed-error.png" display=inline-block/> {:/}

		For details, see [Viewing status for pipeline builds]({{site.baseurl}}/docs/pipelines/monitoring-pipelines/#viewing-status-for-pipeline-builds).

		### GitOps: Helm-based Hybrid Runtimes
		As part of our ongoing commitment to improving efficiency and simplifying installations, we have transitioned from the previous CLI-based installation method to native Kubernetes installation using Helm charts. This change simplifies the installation process and aligns with industry-standard practices for Kubernetes deployments.

		Helm installation for Hybrid GitOps
		Moving forward, we are deprecating the CLI-based installation method for Hybrid GitOps Runtimes. Helm provides better control and ensures compatibility, enabling you to seamlessly manage GitOps Runtimes deployments across various clusters.
		For details, see [Hybrid GitOps Runtime installation]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops-helm-installation/).

		<!---
		* On-Premises version of Codefresh GitOps Runtime
		We also introduced an on-premises version of the GitOps Runtime, allowing you to deploy and manage your Codefresh infrastructure within your private network.
		The on-premises version gives you greater control over your environment, ensuring data security and compliance while leveraging the powerful features and integrations of Codefresh GitOps and Argo CD.
		For details, see [On-premises GitOps Runtime installation]({{site.baseurl}}/docs/installation/gitops/on-prem-gitops-runtime-install/).
		-->

		## Bug fixes
		General
		* Unable to add users to Codefresh via team sync for Okta.


		Pipelines
		* Pipeline builds terminate with error message: `Pipeline could not be executed because retry attempts limit has been exceeded...`.
		* Discrepancy in list of builds returned when running `GET {{baseUrl/workflow?pipeline=[pipeline-id]}}` query.
		* Shallow clone for a specific revision with `depth` argument results in error: `pathspec 'test' did not match any file(s) known to git`.
		* Composition stops randomly with error: `Could not get status for container <container-name>`.
		* Unable to define CRON triggers for pipelines.
		* Cross-account ECR pull in `freestyle` step fails with `(HTTP code 500) server error...`.
		* In the Builds page, steps are grayed out, and the Output tab for a step displays `loading` instead of the step logs.
		* Creating a Git trigger for a repo name containing spaces fails with error: `Failed to create trigger...fails to match the required pattern...`.
		* Unable to set `requiredAvailableStorage` programmatically for Hybrid Pipeline Runtimes.
		* 404 errors on clicking documentation links in Build > Triggers.

		GitOps
		* Unable to delete Argo CD application from Git Source.
		* Same application shows different statuses in the Home > GitOps Dashboard and in the GitOps Apps dashboard.
		* Images not displayed in Images dashboard for GitLab Git provider (Denis)
		* (On premises) Rollouts Reporter for managed cluster uses SaaS instead of on-premises URL.