-
Make your changes in a new branch
-
Update
CHANGELOG.md
, if the change is user-affecting (docs changes or lint fixes don't have to cause changelog/version bumps)-
Ensure correct version bump to a
(WIP)
(Work In Progress) version. -
Always compare to the latest released version for if it should be a major, minor, or patch version bump, according to SemVer 2.0.0.
-
Add a new version with
(WIP)
instead of date, if none exists. There should always be at most 1(WIP)
version.
-
-
Update version in
galaxy.yml
if it's out of date. -
Create a PR targeting
main
branch.
-
Ensure version in
galaxy.yml
is up to date with what's latest inCHANGELOG.md
. -
Change
(WIP)
inCHANGELOG.md
to today's date, in(YYYY-MM-DD)
format. E.g(2022-08-23)
. -
Commit and push to new branch, e.g
release/0.1.0
, and create a PR. -
Wait until after PR has been merged into
main
before continuing. -
Build the collection tarball. Do make sure you're on the latest commit first.
$ git checkout main $ git pull $ make Building 0.1.0 ansible-galaxy collection build --force Created collection for riskident.luks at riskident-luks-0.1.0.tar.gz
-
Upload tarball to Ansible Galaxy namespace
riskident
.Can be done via command line or via website. Docs: https://docs.ansible.com/ansible/devel/dev_guide/developing_collections_distributing.html#publishing-your-collection
-
Create release: https://github.com/RiskIdent/ansible-collection-luks/releases/new
- "Choose a tag": enter version, e.g
0.1.0
, and click + Create new tag: 0.1.0 on publish - Paste the release notes from the
CHANGELOG.md
into the description - Click Publish release
- "Choose a tag": enter version, e.g