@Kevin Crull could you add a license file?

Any chance for a new release of stdlib? several of the fixes in the current code tree would be helpful for my workflows

Why was there a major stdlib release? https://github.com/puppetlabs/puppetlabs-stdlib/releases/tag/v10.0.0. There was no warning in advance, there are zero breaking changes in the changelog.

Half of the ecosystem depends on this module. It creates a ton of work to update other modules for latest stdlib. In the past, such big releases were planned and discussed and tested in advance. Why didn't this happen for the 10.0.0 release?

And from a quick look:the only breaking change is in lib/puppet/parser/functions/validate_augeas.rb? And that could have been avoided?

@bastelfreak: A new version has not been released since the end of 2024 and there was a request to get one out. The major version bump was required because of the change in required Puppet version. This should have been in the changelog which I've already flagged earlier this morning with the engineering team. I do apologize if there were previously some sort of communications done to give a heads up about this, but the majority of the changes in this release have been merged in and available in the main branch for quite some time.

There was no need to bump the minimum puppet version

This could have been a minor release

Now Perforce has to release so so many of their other modules as well. And since they often depend on each other, you will run into a dependency hell.

I highly recommend to delete the 10.0.0 release on the forge and fix the code

I will connect with engineering to see if there is a concern with this. There were no concerns raised by engineering with this change.

yeah but how many people in engineering actually use Puppet and know the impact of a major stdlib release?...

I have passed along the concerns and the request for a rollback to change it over to a minor release without breaking for Puppet 7 users. I'll let everyone know as I learn more.

thank you

The engineering team did validate that the puppetlabs modules ecosystem had the proper upper bounds so they would have stayed on stdlib 9 even with stdlib 10 out there. The Puppet team could roll out updates to the modules to use the new version 10 as needed, once it is made available in the future. The team does want to be able to remove support for Puppet 7 from these modules at some point and a version 10 of

stdlib

is likely going to be needed to do that. If there are modules in the ecosystem that do not have upper bounds, they would be impacted, so this is a good time to be planning for reviewing that impact. Perhaps a good thing to align with the upcoming v9 releases of Puppet Core and OpenVox?

module metadata files all have upper bounds, but the issue is that the upper bound needs to be changed on every module to allow version 10

I think a major version that drops Puppet 7 support would be fine along with some other substantial changes. just changing the lower bound by itself doesn't seem worth a release.

There were several other updates in the release, not just the drop of the Puppet 7 version support, but that was the sticking point that caused it to be a major version and not a minor. So we need to go back to the board and detangle some pieces so we can get out the features that people want without forcing a huge update process across the ecosystem right now. But that version update is going to have to happen, so let's find a way to make it smoother than us just randomly dropping a new v10 out there. If we're deliberate about it, I think it can be smooth.

Some of you already followed along with the above chat around stdlib 10, I've now posted up on puppet.com and dev.to/puppet to share about the upcoming major release: • https://www.puppet.com/blog/puppetlabs-stdlib-10 • https://dev.to/puppet/what-you-need-to-know-about-the-new-puppetlabs-stdlib-10-in-june-2026-1jah

Anyone by chance know if there is a Puppet module to install the "Icinga for WIndows" framework/plugins stuff... Seems odd that they're going to deprecate the Windows plugins in favor of the powershell framework but have no nice way to install it

@Pat Riehecky has left the channel

Hi all, I wonder if I could get a review of this one? github.com/puppetlabs/puppetlabs-stdlib/pull/1479

Also a PR to fix the broken build github.com/puppetlabs/puppetlabs-stdlib/pull/1481 (It could be the wrong approach!)

Also github.com/simp/pupmod-simp-pupmod/pull/244

Thanks for the PRsd @alexharvey! I'll make sure to take a look at them this week at some point to get them into the prioritization queue for engineering.

Hello, I’m using the puppet_operational_dashboards module. Grafana, Influx, and Telegraf are all working fine. All dashboards have data and function correctly, except for the system dashboard (v1 and v2), which doesn’t display any data. Can you please help me identify what I might be missing? My primary/compilers have these classes included. I have a separate host where I run the grafana stack.

- puppet_operational_dashboards::enterprise_infrastructure
  - puppet_operational_dashboards::telegraf::agent

For anyone using the puppet-grafana module: I just release v15.0.1 with the fix for the package resource type

@Jason St-Cyr - any update on this given we're 2 months on? github.com/puppetlabs/puppetlabs-java/pull/628

Hi! could I get a review of these PRs to fix issues around deb822 apt sources (for the puppetlabs-apt module) • support key and pin github.com/puppetlabs/puppetlabs-apt/pull/1301 • use include and normalize architecture github.com/puppetlabs/puppetlabs-apt/pull/1305

hi 🙋... can i get an review for this? 🙂 github.com/puppetlabs/puppetlabs-postgresql/pull/1717