PKCE Login
To improve the security of your OAuth and authentication provider implementations, Salesforce recently released supports for OAuth 2.0 Proof Key for Code Exchange (PKCE) extension.
Previously, customers who enabled PKCE in their orgs were unable to sign in to Copado Essentials due to the requirement for additional code verifiers and code challenges.
With this release, we have added PKCE support to the Copado Essentials OAuth flow, allowing users to sign in seamlessly, whether PKCE is enabled in their orgs or not.
Salesforce API 63.0 Upgrade
With the release of Spring '25 across all Salesforce instances, we have upgraded Copado Essentials to the latest API version 63.0. All org-to-org deployments now utilize API version 63.0 for comparing, retrieving, and deploying metadata. Git deployments will continue to follow the version specified in your Git repository.
Pipeline Validation Update
Some users previously faced issues creating new work items because the initial organization in the pipeline was not shared properly. We have refined the validation rule to exclude the initial org from sharing requirements when creating work items. This change ensures smoother creation, as the initial org in a pipeline is always replaced by the user-selected/personal sandboxes at the time of creation.
In the example below, the first org in the pipeline will be Dev 2, replacing the pipeline template org Dev.
Deploy Specific Flow Version
Previously, Essentials only allowed users to deploy the latest version of a flow. However, many users have asked for the flexibility to deploy the active version instead, which may not always be the latest.
With this release, we're giving users more control over flow deployments by allowing them to select and deploy a specific version of a flow.
To deploy a specific version, click on "Change Flow Version" and choose the version you'd like to deploy.
