Puppet Community

no. My understanding is that aio releases are scheduled and require a lot of planning, builds for many architectures, release notes, and so on

thats not required if you "just" tag a new gem release

The `puppet-agent` package (a.k.a. AIO) also includes a vendored copy of the `concurrent-ruby` gem. So, a new AIO build shouldn't be needed as this gem shouldn't be updated outside of upgrading the `puppet-agent` package.

`bundle install` is different in that it re-solves dependencies whenever it gets run -- so it is picking up yesterday's release of concurrent-ruby 1.2.0 and pulling it in to satisfy Puppet's `concurrent-ruby ~&gt; 1.0` dependency.

that makes me wonder why they tagged it as 6.29.0 and not 6.28.1 / 7.21.1

mhm were there more changes in the release?

yes <https://github.com/puppetlabs/puppet/compare/7.21.0...7.22.0>

that makes sense, guess they didn't want to do a 7.21-stable branch just for that

<https://github.com/puppetlabs/puppet/commit/a94db64910381add4428a7654d867ad023d27844> looks like also some fixes for Ruby 3.2 support

probably nowhere near complete, but good to see it's being worked on

I'll have to start looking into it for Fedora 38, which has bumped to Ruby 3.2 (since I co-maintain Puppet on Fedora)

ewoud: <https://github.com/puppetlabs/puppetlabs-postgresql/pull/1386#issuecomment-1402065399> but when you run `bundle install`, is there any guarantee bundler prefers the newer puppet gem over the newer concurrent_ruby??

VoxBot_: no idea and I wondered the same thing

afisher: I'd guess that puppet is listed in Gemfile, so would have higher prio but no idea if that's a real thing

I guess I should have tested this theory out earlier today by adding the dependency to a random in house puppet lint plugin. Might have been less painful than the 35 individual PRs I ended up opening…

Cross posting: <https://puppetcommunity.slack.com/archives/C0W298S9G/p1674608846284439>

<https://github.com/voxpupuli/facterdb/pull/264> Our first gem with Ruby 3.2 support \o/

<https://github.com/theforeman/puppet-foreman_proxy/actions/runs/4004881478/jobs/6874585735> looks like puppetlabs_spec_helper 5 broke every test suite we have

interesting, haven't seen that on vox pupuli. I think we still pull 4.0.1 in

<https://github.com/voxpupuli/puppet-borg/actions/runs/4004570685/jobs/6873871406#step:3:204> ah no, 5.0.1. works for us

I just wanted to add a missing `requires`!

bastelfreak: <https://github.com/theforeman/puppet-foreman_proxy/blob/master/.fixtures.yml> there we do have hashes inside the repositories while <https://github.com/voxpupuli/puppet-borg/blob/master/.fixtures.yml> only has strings, perhaps that's the difference?

<https://github.com/theforeman/puppet-foreman_proxy/pull/797> if that passes, we'll know