Playbook for releasing fleeting-plugin-aws to gitlab.com

Context: https://gitlab.slack.com/archives/C0199KBMY59/p1677864216085049:

Arran Walker: Be good if we could tag a new release of aws fleeting plugin. Not sure if we want v0.1.0 or v0.0.2 whilst we’re developing like we are

Davis: I’d probably lean towards calling anything a minor release if we aren’t guaranteeing anything at this point, just to indicate any upgrade could be more significant… but if we want to be proper about it, what has changed since the last tag?

Joe: yeah, i would say if we’re just trying to get the latest code and features out there, let’s bump the minor version (v0.1.0 … v0.2.0). if we are cherry picking a bug fix, we’ll bump the patch

Joe: and once you do release, please bump the version in the chef cookbook to deploy to gitlab.com: https://gitlab.com/gitlab-cookbooks/cookbook-gitlab-runner/-/blob/f7c3e5ec56abdef28e52dbd80e8f9a0c42d79485/attributes/default.rb#L16 and bump the cookbook version: https://gitlab.com/gitlab-cookbooks/cookbook-gitlab-runner/-/blob/f7c3e5ec56abdef28e52dbd80e8f9a0c42d79485/metadata.rb#L7. if we are only releasing a new plugin, let’s bump the cookbook patch version (1.5.0 -> 1.5.1). no new cookbook features

Joe: and let’s write this process down! gitlab-org/ci-cd/shared-runners/images/macstadium/orka#123 (moved)