Puppet Community

```      "name": "puppetlabs-firewall",
...
      "name": "puppet-firewalld",```
:thinking_face:

See the `puppetlabs-firewall` module at <https://forge.puppet.com/puppetlabs/firewall?src=slack&amp;channel=voxpupuli>

hmm.. maybe we should tune the bot a bit to not suggest modules here :slightly_smiling_face:

<https://github.com/voxpupuli/puppet-k8s/pull/31> &lt;- s/herculesteam/puppet/

<@U1PC2RAH0> shall I change all modules in the .fixtures to git version?

meh.. now I hit the:
```Unable to resolve modules: Puppetfile Resolver could not find compatible versions for possibility named "augeasproviders_sysctl":
  In Puppetfile:
    -k8s &gt;= 0 was resolved to Git puppet-k8s-0.0.1, which depends on
      puppet-augeasproviders_sysctl &gt;= 2.6.2 &lt; 3.0.0```

ah.. so modules were not released after they were moved to voxpupuli..

<https://github.com/voxpupuli/puppet-augeasproviders_sysctl/pull/65>

I’d use sysfsutils package instead of patching sysctl.conf..

reproduced the issue above on my laptop with docker beaker:
`BEAKER_PUPPET_COLLECTION=puppet7 BEAKER_setfile='ubuntu2004-AARCH64{docker_preserve_image=true}' bundle exec rake beaker`

``` ~/src/puppet-network  rel/1.0.2 +2  be rake release                                                                                                                                      INT ✘  16:39:08
To use retry middleware with Faraday v2.0+, install `faraday-retry` gem
Cleaning for module build
Bumping version from 1.0.2 to 1.0.3-rc0
rake aborted!
Blacksmith::Error: Command ["git", "--git-dir", "/Users/nate/src/puppet-network/.git", "--work-tree", "/Users/nate/src/puppet-network", "push"] failed with exit status pid 21441 exit 128
fatal: The current branch rel/1.0.2 has no upstream branch.
To push the current branch and set the remote as upstream, use

    git push --set-upstream origin rel/1.0.2

To have this happen automatically for branches without a tracking
upstream, see 'push.autoSetupRemote' in 'git help config'.

/Users/nate/src/puppet-network/.vendor/ruby/2.7.0/gems/puppet-blacksmith-6.1.1/lib/puppet_blacksmith/git.rb:85:in `exec_git'
/Users/nate/src/puppet-network/.vendor/ruby/2.7.0/gems/puppet-blacksmith-6.1.1/lib/puppet_blacksmith/git.rb:62:in `push!'
/Users/nate/src/puppet-network/.vendor/ruby/2.7.0/gems/voxpupuli-release-2.0.0/lib/voxpupuli/release/rake_tasks.rb:75:in `block in &lt;top (required)&gt;'
/Users/nate/src/puppet-network/.vendor/ruby/2.7.0/gems/rake-13.0.6/exe/rake:27:in `&lt;top (required)&gt;'
/Users/nate/.rbenv/versions/2.7.7/bin/bundle:23:in `load'
/Users/nate/.rbenv/versions/2.7.7/bin/bundle:23:in `&lt;main&gt;'
Tasks: TOP =&gt; release
(See full trace by running task with --trace)```

I feel like those docs are.... maybe leaving out some things?
Like, should I be in a branch? Should I be using a fork? Do I commit any of those changes manually before running `be rake release`?

Ah, nvm, I see the instructions about what branch to be in (`master`). Trying again...

But do I need to manually update  the version in `metadata.json`?

uhh... no, that didn't seem to work either:
``` ~/src/puppet-network  master !2  be rake release                                                                                                  
To use retry middleware with Faraday v2.0+, install `faraday-retry` gem
rake aborted!
Refusing to release an RC or build-release (1.0.1-rc0).
Please set a semver *release* version.
/Users/nate/src/puppet-network/.vendor/ruby/2.7.0/gems/voxpupuli-release-2.0.0/lib/voxpupuli/release/rake_tasks.rb:55:in `block in &lt;top (required)&gt;'
/Users/nate/src/puppet-network/.vendor/ruby/2.7.0/gems/rake-13.0.6/exe/rake:27:in `&lt;top (required)&gt;'
/Users/nate/.rbenv/versions/2.7.7/bin/bundle:23:in `load'
/Users/nate/.rbenv/versions/2.7.7/bin/bundle:23:in `&lt;main&gt;'
Tasks: TOP =&gt; release
(See full trace by running task with --trace)
 ~/src/puppet-network  master !2  vim metadata.json                                                                                                
 ~/src/puppet-network  master !2  vim metadata.json                                                                                                
 ~/src/puppet-network  master !2  be rake release                                                                                                  
To use retry middleware with Faraday v2.0+, install `faraday-retry` gem
Cleaning for module build
Bumping version from 1.0.2 to 1.0.3-rc0
 ~/src/puppet-network  master !1  gst                                                                                                              
On branch master
Your branch is up to date with 'origin/master'.

Changes not staged for commit:
  (use "git add &lt;file&gt;..." to update what will be committed)
  (use "git restore &lt;file&gt;..." to discard changes in working directory)
        modified:   CHANGELOG.md

no changes added to commit (use "git add" and/or "git commit -a")```

See the `puppet-network` module at <https://forge.puppet.com/puppet/network?src=slack&amp;channel=voxpupuli>

isn't <https://voxpupuli.org/docs/releasing_version/> clear that you should create a release PR, before running the release rake task?

you also did publish a release, 1.0.2-rc0

you can update it manually or with a rake task, before running the changelog task

did you actually read the docs you linked? :)

the second sentence is `Create a â€˜release prâ€™. `

"This pull request updates the changelog and bumps the version number to the target version"

and after all this, way and the end, the docs say "bundle exec rake release". you missed a few steps

I did :slightly_smiling_face: but obviously misunderstand them, sorry.

re-reading now.... is it setup as two possible options?
Either:
a) Make a release PR
OR
b) run the rake tasks