Continuous Delivery for PE 5.19.0 is here! # Continuous Delivery (CD4PE) 5.19.0 Release Notes Continuous Delivery (CD4PE) 5.19.0 makes it faster, more reliable, and more secure. You get refreshed console pages, updated platform components, and fixes across Impact Analysis, source control integrations, and deployments. Read the full details in the [release notes](https://help.puppet.com/cdpe/current/Content/UserGuide/CDPE/ReleaseNotes/cd_release_notes.htm#Version5190). ## Highlights • Refreshed pages: Root console settings pages and deployment and Impact Analysis details pages look better and run faster. • Impact Analysis memory: We reduced the memory usage that went up in 5.18.0. • Easier 5.18.0 upgrades: The ssl_crl Hiera key is now optional, which fixes upgrade failures when it held a certificate instead of a valid CRL. • Safer database restores: A failed restore now stops and shows the pg_restore error instead of reporting success. During upgrades, your pre-upgrade backup stays intact for rollback. • Custom deployments: The public cd4pe_deployments repository is now a mirror of an internal fork. It’s still the reference for custom deployments. File bugs and feature requests as GitHub issues. • Job image update: The default puppet-dev-tools:puppet8 image now uses puppetlabs forks of several tooling gems. The onceover command still works. • And more: We also fixed issues with sessions, API errors, webhooks, and Bitbucket Cloud. ## Security Updates • GraphQL authorization: We fixed an issue that let authenticated users access Puppet data and change saved views across workspaces. • Login redirects: Login now only redirects to pages inside CD. • GitLab: We tightened validation on project identifiers, branch names, and file paths. CD no longer follows redirects on requests that carry the integration token. • Dependencies: We updated third-party dependencies to fix a large set of CVEs. The release notes list them all. ## What to do next 1. Read the [5.19.0 release notes](https://help.puppet.com/cdpe/current/Content/UserGuide/CDPE/ReleaseNotes/cd_release_notes.htm#Version5190) before you upgrade. 2. Upgrade if you're running 5.18.0 and have experienced elevated Impact Analysis memory usage. If you configured a larger heap for CD on 5.18.0, you can revert that change. 3. If you use GitLab integrations, rotate existing personal access tokens and consider using a dedicated service account with only the required repository permissions. 4. Validate any custom deployment workflows that use the cd4pe_deployments repository and review the updated maintenance model. 5. Review security advisories if your organization tracks vulnerabilities at the CVE level and schedule an upgrade window to apply the included fixes. --- The Puppet Team Sent by Zapier