# Who can approve Pull Requests on molecule-plugins and do releases? **URL:** \ **Category:** Project Discussions\ **Tags:** molecule\ **Created:** [July 1, 2026, 3:34pm UTC](https://forum.ansible.com/t/who-can-approve-pull-requests-on-molecule-plugins-and-do-releases/46015 "2026-07-01T15:34:05Z")\ **Posts on this page:** 18\ **Page:** 1
**Author:** ![ziegenberg](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/ziegenberg/32/438_2.png) [@ziegenberg](https://forum.ansible.com/u/ziegenberg)\ **Post date:** [July 1, 2026, 3:34pm UTC](https://forum.ansible.com/t/who-can-approve-pull-requests-on-molecule-plugins-and-do-releases/46015/1 "2026-07-01T15:34:05Z")
Hi all together! Molecule was just recently released in version [v26.6.0](https://github.com/ansible/molecule/releases/tag/v26.6.0), and there were about seven other releases in the last year. Molecule Plugins is still at the same state as last year, and [v25.8.12](https://github.com/ansible-community/molecule-plugins/releases/tag/v25.8.12) was released in August 2025. There are [35 open Pull Requests](https://github.com/ansible-community/molecule-plugins/pulls) waiting for review and approval: half fixing things, the other half adding features. I asked in the Matrix room [#devtools:ansible.com](https://matrix.to/#/#devtools:ansible.com) twice and received no response, so I’m hoping someone here can help. The project is in poor shape and falling behind the rapid development of Ansible, and even behind Molecule itself. Greetings, Daniel ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [July 1, 2026, 3:57pm UTC](https://forum.ansible.com/t/who-can-approve-pull-requests-on-molecule-plugins-and-do-releases/46015/2 "2026-07-01T15:57:46Z")
I’d guess that @cidrblock and @ssbarnea still have the necessary rights. But 🤷 ---
**Author:** ![ziegenberg](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/ziegenberg/32/438_2.png) [@ziegenberg](https://forum.ansible.com/u/ziegenberg)\ **Post date:** [July 1, 2026, 4:12pm UTC](https://forum.ansible.com/t/who-can-approve-pull-requests-on-molecule-plugins-and-do-releases/46015/3 "2026-07-01T16:12:34Z")
The first PR to review and merge should be: [fix: docker driver compatibility with ansible-core 2.21 by wh-zfy · Pull Request #364 · ansible-community/molecule-plugins · GitHub](https://github.com/ansible-community/molecule-plugins/pull/364) ---
**Author:** ![ziegenberg](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/ziegenberg/32/438_2.png) [@ziegenberg](https://forum.ansible.com/u/ziegenberg)\ **Post date:** [July 7, 2026, 1:06pm UTC](https://forum.ansible.com/t/who-can-approve-pull-requests-on-molecule-plugins-and-do-releases/46015/4 "2026-07-07T13:06:28Z")
Nothing has happened so far. @felixfontein, do you know who I can get in touch with to get an answer? ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [July 7, 2026, 7:38pm UTC](https://forum.ansible.com/t/who-can-approve-pull-requests-on-molecule-plugins-and-do-releases/46015/5 "2026-07-07T19:38:58Z")
Maybe the [@CommunityEngTeam](https://forum.ansible.com/groups/communityengteam) can help. ---
**Author:** ![ziegenberg](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/ziegenberg/32/438_2.png) [@ziegenberg](https://forum.ansible.com/u/ziegenberg)\ **Post date:** [July 8, 2026, 3:17pm UTC](https://forum.ansible.com/t/who-can-approve-pull-requests-on-molecule-plugins-and-do-releases/46015/6 "2026-07-08T15:17:58Z")
Surprise! It turns out I myself can approve pull requests for “molecule-plugins.” 😃 And that’s exactly what I’ve just done. ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [July 8, 2026, 3:33pm UTC](https://forum.ansible.com/t/who-can-approve-pull-requests-on-molecule-plugins-and-do-releases/46015/7 "2026-07-08T15:33:51Z")
Congrats on commit rights 🙂 ---
**Author:** ![ziegenberg](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/ziegenberg/32/438_2.png) [@ziegenberg](https://forum.ansible.com/u/ziegenberg)\ **Post date:** [July 8, 2026, 5:50pm UTC](https://forum.ansible.com/t/who-can-approve-pull-requests-on-molecule-plugins-and-do-releases/46015/8 "2026-07-08T17:50:51Z")
But I still need someone else to review my PRs ---
**Author:** ![ziegenberg](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/ziegenberg/32/438_2.png) [@ziegenberg](https://forum.ansible.com/u/ziegenberg)\ **Post date:** [July 14, 2026, 4:17pm UTC](https://forum.ansible.com/t/who-can-approve-pull-requests-on-molecule-plugins-and-do-releases/46015/9 "2026-07-14T16:17:34Z")
And I did a release. But now I need to move this forward: [Initial import by apatard · Pull Request #7 · ansible-collections/community.vagrant · GitHub](https://github.com/ansible-collections/community.vagrant/pull/7) Any ideas who could help? ---
**Author:** ![dbrennand](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dbrennand/32/7830_2.png) [@dbrennand](https://forum.ansible.com/u/dbrennand)\ **Post date:** [August 31, 2026, 1:20pm UTC](https://forum.ansible.com/t/who-can-approve-pull-requests-on-molecule-plugins-and-do-releases/46015/10 "2026-08-31T13:20:44Z")
Hey @ziegenberg Thank you for your work on the `molecule-plugins` and the `community.vagrant` collection so far. I’d like to offer my assistance with helping maintain `molecule-plugins` and `community.vagrant` 🙂 ## Molecule Plugins Is there any specific area you’d like me to look at first? FYI I forked [`molecule-plugins`](https://github.com/dbrennand/molecule-plugins/pulls?q=is%3Apr+is%3Aclosed) 3 weeks ago and have been chipping away in my fork at trying to do some tidy up which I think is related to some work you were doing too in [chore: replace pre-commit with prek and align lint tooling with molecule by ziegenberg · Pull Request #384 · ansible-community/molecule-plugins · GitHub](https://github.com/ansible-community/molecule-plugins/pull/384), I had planned to eventually submit these changes back to `ansible-community/molecule-plugins`: Do you think this would be beneficial? Full disclosure, I used AI to assist me with these changes: - [chore: remove pre-commit.ci configuration by dbrennand · Pull Request #1 · dbrennand/molecule-plugins · GitHub](https://github.com/dbrennand/molecule-plugins/pull/1) - [chore: remove duplicate pre-commit hooks by dbrennand · Pull Request #2 · dbrennand/molecule-plugins · GitHub](https://github.com/dbrennand/molecule-plugins/pull/2) - [chore: simplify linting configuration by dbrennand · Pull Request #3 · dbrennand/molecule-plugins · GitHub](https://github.com/dbrennand/molecule-plugins/pull/3) - [chore: migrate linting to prek by dbrennand · Pull Request #4 · dbrennand/molecule-plugins · GitHub](https://github.com/dbrennand/molecule-plugins/pull/4) - [chore: narrow Ruff cleanup by dbrennand · Pull Request #5 · dbrennand/molecule-plugins · GitHub](https://github.com/dbrennand/molecule-plugins/pull/5) ## Community Vagrant I checked the collection and there is linter configuration for: black, mypy, pylint, flake8, ruff, and yamllint. That’s a lot of linters 😃 - What are your thoughts about using ruff and ansible-lint. Ansible Lint runs yamllint and has its own internal ruleset we could have compatibility with. It would also reduce the number of configuration files in the repo too, and help reduce long term maintenance burden. Also, now that the vagrant driver has been migrated to `community.vagrant`, I believe the original intent was to direct users to adopt that and deprecate the driver in `molecule-plugins`? ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [August 31, 2026, 3:33pm UTC](https://forum.ansible.com/t/who-can-approve-pull-requests-on-molecule-plugins-and-do-releases/46015/11 "2026-08-31T15:33:52Z")
> [@dbrennand](#): > > ## > > I checked the collection and there is linter configuration for: black, mypy, pylint, flake8, ruff, and yamllint. That’s a lot of linters 😃 - What are your thoughts about using ruff and ansible-lint. Ansible Lint runs yamllint and has its own internal ruleset we could have compatibility with. It would also reduce the number of configuration files in the repo too, and help reduce long term maintenance burden. While ruff can cover black and flake8, it can only cover a subset of pylint. Because of that, removing pylint from the list sounds like a bad idea to me. ---
**Author:** ![ziegenberg](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/ziegenberg/32/438_2.png) [@ziegenberg](https://forum.ansible.com/u/ziegenberg)\ **Post date:** [August 31, 2026, 4:24pm UTC](https://forum.ansible.com/t/who-can-approve-pull-requests-on-molecule-plugins-and-do-releases/46015/12 "2026-08-31T16:24:07Z")
Hi @dbrennand, I’d love to see some support in maintaining `molecule-plugins` and `community.vagrant`. I’ll incorporate some of your changes into the current PR work to reorganise the tooling. I want to align it with the upstream molecule project, so both have similar DX. I’d love to get your review of the PRs so we can merge them. Regarding `community.vagrant`: > Also, now that the vagrant driver has been migrated to `community.vagrant`, I believe the original intent was to direct users to adopt that and deprecate the driver in `molecule-plugins`? That’s why there is [Fix vagrant module in playbooks by 0x4D616E75 · Pull Request #314 · ansible-community/molecule-plugins · GitHub](https://github.com/ansible-community/molecule-plugins/pull/314) Greetings, Daniel ---
**Author:** ![dbrennand](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dbrennand/32/7830_2.png) [@dbrennand](https://forum.ansible.com/u/dbrennand)\ **Post date:** [August 31, 2026, 9:02pm UTC](https://forum.ansible.com/t/who-can-approve-pull-requests-on-molecule-plugins-and-do-releases/46015/13 "2026-08-31T21:02:13Z")
> [@felixfontein](#): > > While ruff can cover black and flake8, it can only cover a subset of pylint. Because of that, removing pylint from the list sounds like a bad idea to me. Good point, thanks @felixfontein. I was just reading up some more on [How does Ruff’s linter compare to Pylint?](https://docs.astral.sh/ruff/faq/#how-does-ruffs-linter-compare-to-pylint) 🙂 TIL. > [@ziegenberg](#): > > That’s why there is [Fix vagrant module in playbooks by 0x4D616E75 · Pull Request #314 · ansible-community/molecule-plugins · GitHub](https://github.com/ansible-community/molecule-plugins/pull/314) OK, I was referring to the removal of the vagrant driver entirely from `src/molecule_plugins/vagrant`, if not, future changes to the vagrant plugin in `molecule-plugins` will need to be continuously backported to `community.vagrant`? Now that `community.vagrant` is seeded with the vagrant module, should we create some documentation to assist folks with migrating to use the collection module rather than the driver. ---
**Author:** ![dbrennand](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dbrennand/32/7830_2.png) [@dbrennand](https://forum.ansible.com/u/dbrennand)\ **Post date:** [September 26, 2026, 8:32pm UTC](https://forum.ansible.com/t/who-can-approve-pull-requests-on-molecule-plugins-and-do-releases/46015/14 "2026-09-26T20:32:01Z")
Hey @ziegenberg Today I made some good progress on merging some critical bug fixes and security related PRs into `molecule-plugins` - I also created and pinned [Project Maintenance Update · Issue #388 · ansible-community/molecule-plugins · GitHub](https://github.com/ansible-community/molecule-plugins/issues/388) to notify folks that we are working on bringing the project back to a healthy state 🙂 - Hopefully I should be able to cut a new release in the coming days 🙂 ---
**Author:** ![ziegenberg](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/ziegenberg/32/438_2.png) [@ziegenberg](https://forum.ansible.com/u/ziegenberg)\ **Post date:** [September 27, 2026, 10:14am UTC](https://forum.ansible.com/t/who-can-approve-pull-requests-on-molecule-plugins-and-do-releases/46015/15 "2026-09-27T10:14:21Z")
Hi @dbrennand, I’ll look at this today in the late afternoon (European time zone). Greetings, Daniel ---
**Author:** ![dbrennand](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dbrennand/32/7830_2.png) [@dbrennand](https://forum.ansible.com/u/dbrennand)\ **Post date:** [September 27, 2026, 10:18am UTC](https://forum.ansible.com/t/who-can-approve-pull-requests-on-molecule-plugins-and-do-releases/46015/16 "2026-09-27T10:18:05Z")
@ziegenberg Awesome! I added you as a reviewer to a couple of PRs too for some other bug fixes. Thanks! ---
**Author:** ![simi](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/simi/32/11291_2.png) [@simi](https://forum.ansible.com/u/simi)\ **Post date:** [October 8, 2026, 5:25am UTC](https://forum.ansible.com/t/who-can-approve-pull-requests-on-molecule-plugins-and-do-releases/46015/17 "2026-10-08T05:25:36Z")
Hello, I’m happy to help also. Currently I’m looking for a way to sneak [feat(lima): Add Lima driver by simi · Pull Request #387 · ansible-community/molecule-plugins · GitHub](https://github.com/ansible-community/molecule-plugins/pull/387) in. Happy to maintain that driver once merged. I can also help with basic maintenance. ---
**Author:** ![dbrennand](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dbrennand/32/7830_2.png) [@dbrennand](https://forum.ansible.com/u/dbrennand)\ **Post date:** [October 9, 2026, 7:49am UTC](https://forum.ansible.com/t/who-can-approve-pull-requests-on-molecule-plugins-and-do-releases/46015/18 "2026-10-09T07:49:57Z")
Discussions ongoing on Matrix: [You're invited to talk on Matrix](https://matrix.to/#/!aqMMMrOxRZzVDkUlWF:matrix.org/$bZTIKrHnQD3aiK5M_VOvXf73JbkhXYE4FjITZOoPnnw?via=ansible.com&via=matrix.org&via=ansible.im)