PE 2025.3.0

Released May 2025

Puppet Enterprise (PE) 2025 is our leading-edgePE release stream (also referred to as STS).

For important information about upgrading to 2025, see Upgrading Puppet Enterprise.
If you're on the LTS stream (2023.8), you'll find release notes and other information for that series in the 2023.8 documentation.
Customers on 2021.7.z, which is EOL, are encouraged to upgrade to 2023.8.z.
To access End-of-Life (EOL) dates and maintenance information, see PE End-of-Life (EOL).

To access the release notes for the Puppet^® platform, including Puppet agent, Puppet Server, Facter, and PuppetDB, see Platform release notes.

Enhancement

Pruning process added to activity service for old activity data

In PE 2025.3.0 and 2023.8.3, the activity service runs a cleanup process periodically to prune old activity data. When versions 2025.3.0 and 2023.8.3 are installed, the activity service begins to purge entries older than 13 months upon installation. The threshold for data defaults to 13 months and is configurable.

There are three new configuration values in relation to the activity pruning process:

puppet_enterprise::profile::console::activity_purge_interval

This configures the interval between purge operations in milliseconds.

Default: 1800000 (30 minutes).

puppet_enterprise::profile::console::activity_purge_limit

This configures the max number of activity entries each individual purge operation will attempt to delete.

Default: 200,000 (rows).

puppet_enterprise::profile::console::activity_purge_after

This configures the number of days after which data will start to be deleted.

Default: 395 (13 months).

Advanced Patching API: New endpoint added

post__v1_command_delete-patch-job: Delete a patch job and its remaining schedule.

Platform support

Agent platforms added

This release adds support for the Puppet agent on the following operating system platforms:

Amazon Linux 2023 (FIPS)
Microsoft Windows Server 2025

Primary server platforms added

This release adds support for the primary server on the following operating system platforms:

Amazon Linux 2023

Resolved issues

The large file footprint created by the host action collector has been fixed

As part of the host-action-collector, individual events are archived to the filesystem under a year/month/day scenario. For large customers with a large number of files that were large in size, the host-action-collector wrote these files as part of normal operations. Additionally, the host-day files were not cleaned up regularly and/or removed when they weren’t needed anymore. This issue has been fixed in PE 2023.8.3 and 2025.3.0.

When plan_runner_active is set to true, the infra plan no longer throws an error

In PE 2023.6-2023.8.2 and 2025.0.0-2025.2.0, when plan_runner_active was set to true, an error was shown on the command line. This issue has been fixed in 2023.8.3. and 2025.3.0.

Breaking pe_repo::base_url in repo handling fixed

When upgrading from PE 2023.8.1 to 2023.8.2, it was not possible to set pe_repo::base_url to an internal mirror and download all additional agents for other operating systems from this mirror. This issue has been fixed in 2023.8.3 and 2025.3.0.

Unable to edit values for non-string parameters in scheduled plans fixed

In 2021.7.8, users were unable to edit values for non-string parameters in scheduled plans. As a result, scheduled plans needed to be deleted and then, re-created. This issue has been fixed in 2023.8.3 and 2025.3.0.

Advanced Patching: The Overview page no longer displays Enable Advanced Patching details when no nodes have patches available

In PE 2025.2.0, when no nodes had patches available, Enable Advanced Patching details were displayed on the Overview page. This issue has been fixed in 2025.3.0.

Advanced Patching: Creating a patch group uses resolved nodes

In PE 2025.2.0, when creating a new patch group, and rules were specified, the group did not correctly use the resolved nodes when creating the node group. This issue has been fixed in 2025.3.0.

Advanced Patching: Counts on overview no longer fails to account for rules matches

In PE 2025.2.0, the overview counts of security items in patch groups did not take into account nodes that resulted from the dynamic rules for a patch group. This issue has been fixed in 2025.3.0.

Advanced Patching: Resolving rule with non-queryable object no longer throws unhandled exception

In PE 2025.2.0, resolving nodes with a rule that included a non-queryable field resulted in an unhandled exception being thrown. This issue has been fixed in 2025.3.0.

Advanced Patching: Node count on the patch group page no longer fails to account for rules matches

In PE 2025.2.0, with the introduction of the rules to the patch group API, the counts of nodes on the patch group page did not correctly reflect the number of nodes in the group. This issue has been fixed in 2025.3.0.

Advanced Patching: Node purge no longer fails to purge nodes correctly from removed list

In PE 2025.1.0-2025.2.0, node purge failed to purge nodes correctly from the removed nodes list. This issue has been fixed in 2025.3.0.

Security fixes

Addressed the following CVEs:

CVE-2025-21587