community.sops
community.sops copied to clipboard
ansible-collections
Release planning
Let's use this issue to discuss when to release a new version.
I'd like to make a 1.2.0 release soon. We just missed the feature freeze window for Ansible 5.0.0, but we can still get into 4.10.0 and 5.1.0. @endorama what do you think?
Ok for me. Happy to cut the release.
What changes are needed to make the 1.2.0 release?
What are the deadlines?
These are the changes since last release: https://github.com/ansible-collections/community.sops/compare/1.1.0...main
The changes from November 10th are the main parts; the other commits are mainly collection infrastructure.
Deadlines: Ansible 5.1.0 will be out on December 21st, but Ansible 4.9.0 should come out on November 23rd (i.e. in 8 days). So having a release before then would be great IMO :)
I'll make a small 1.2.1 release today with updated docs (README update from November, collection links file from today).
I'll create a 1.2.3 release today to fix a docs formatting issue. That will reduce the number of warnings in the Ansible docs build by three :) CC @samccann
1.3.0 has been released with a new feature to work around an awx information leak when using the vars plugin.
1.4.1 has been released to improve compatibility to future ansible-core releases (regarding the load_vars action plugin).
1.5.0 has been released with a role for installing sops, and two playbooks for installing sops on localhost and remote targets. This makes it easier to use community.sops in Execution Environments.
1.6.1 has been released with a bugfix (doesn't directly affect content in this collection though).
1.6.3 has been released with updated documentation that now uses semantic markup.
Not exactly a release announcement, but: the sops repository moved from https://github.com/mozilla/sops to https://github.com/getsops/sops/! So finally something got moving, and we'll get a new patch release hopefully soon (https://github.com/getsops/sops/discussions/927#discussioncomment-6314749)!
(The only drawback: the installation role breaks, apparently fetching the latest release data from GitHub doesn't like permanent redirects... Will look at it now...)
1.6.4 is out with a fixed install role, and updated references (getsops/sops instead of mozilla/sops).
1.6.6 is out with a fixed install role. Now fully works with today's sops 3.8.0 release! :tada:
1.7.0 is out with a new feature and support for SOPS 3.9.0. Unfortunately the RPM URL changed again, so I decided to cut this release now instead of adding some more feaures first that can be done with 3.9.0...
1.8.0 is out with proper SOPS 3.9.0 support. This includes detecting the SOPS version to use the new subcommands, including the filestatus subcommand to improve handling of unencrypted files for the vars plugin. When SOPS 3.9.0 is used, this release also fixes a long-standing bug for the community.sops.sops_encrypt module.