Cut a new release and publish to forge

[DLeich]

Hey @biemond ! First off, I wanted to say that this module is fantastic. I've now used it at two organizations and it has drastically improved the ability of operations teams and database administrators to maintain and orchestrate their database servers.

The latest release of the module is from August 2019, and there have been several commits since then, mostly focusing on supporting new versions. When can we expect a new release to be cut to include these changes? For now I'm going to pin to the commits which include these changes, pointing directly to github instead of the forge, but I feel it would be more stable and acceptable to use forge tags instead.

Thanks!

[biemond]

Hey, yes . It is more that I don't have a lot of time to test all the versions . But everything is welcome. Let me see if I can still do this

Plus I guess they become more strict now

[DLeich]

Hey @biemond - Just curious if you have any intention to cut a release on the forge? This is a highly used module from multiple organizations and while I"m currently pinning to commits directly here on github, it would be much better practice to consume from the forge directly.

[jeffbyrnes]

Would love to see a new release as well! Happy to help.