Puppet Community

(<@U6B5Q9BSA> is working on improving this)

yes, I was thinking that it wasn't especially interesting as it's mostly just noise from a recent puppet-strings update.

Ideally, the tag would be on the 'Release X' merge commit, but if it's only the REFERENCE.MD changing, (and in non important ways), it _probably_ doesn't matter??

I think, if anything, we probably want the release PR to fail if the file is out of date??

yes it would be nice, but that's about it

<https://github.com/voxpupuli/voxpupuli-release/pull/44> is the PR from <@U6B5Q9BSA>

tl;dr update it during changelog generation

Maybe we need to change our minimum `puppet-strings` version to 3? (To stop any flapping between before and after eg. <https://github.com/puppetlabs/puppet-strings/pull/303>

<https://github.com/voxpupuli/modulesync_config/pull/800>

Any day you get to quote 'The Princess Bride' is a good day. <https://github.com/voxpupuli/voxpupuli-release/pull/47>

I think <https://github.com/voxpupuli/puppet-puppet_certificate/pull/11> is ready for merge.  I'd like to get a release out and then start my next refactor (I'm going to split the code into 2 separate providers)

<@U1PC2RAH0> Copy and paste? <https://github.com/voxpupuli/puppet-consul/pull/593/files#r1011640970> ??

I was looking for some boilerplate to steal for puppet_certificate at the time and randomly picked on that.

<@U5V9MMW9E> <https://github.com/voxpupuli/puppet-consul/pull/619>

Cool.  Dunno if you want to have a quick scan for any other modules this text made it to??

<https://github.com/voxpupuli/puppet-vault/pull/15>