[2138218548] Upstream Reporter: Timothée Ravier
Upstream issue status: Closed
Upstream description:

Release checklist:

Tagging:

• [x] Write release notes in `docs/release-notes.md`. Get them reviewed and merged
• [x] If the release signing key has changed because a new Fedora release has gone stable, note the change as done [here](https://github.com/coreos/butane/releases/tag/v0.12.0).
• [x] If doing a branched release, also include a PR to merge the `docs/release-notes.md` changes into main
• [x] Ensure your local copy is up to date with the upstream main branch (`git@github.com:coreos/butane.git`)
• [x] Ensure your working directory is clean (`git clean -fdx`)
• [x] Ensure you can sign commits and any yubikeys/smartcards are plugged in
• [x] Run `./tag_release.sh <vX.Y.z> <git commit hash>`
• [x] Push that tag to GitHub

Fedora packaging:

• [x] Update the spec file in [Fedora](https://src.fedoraproject.org/rpms/butane):
• Bump the `Version`
• Switch the `Release` back to `1%{?dist}`
• Remove any patches obsoleted by the new release
• Run `go-mods-to-bundled-provides.py | sort` while inside of the `butane` directory you ran `./tag_release` from & copy output into spec file in `# Main package provides` section
• Update changelog
• [x] Run `spectool -g -S butane.spec`
• [x] Run `kinit your_fas_account@FEDORAPROJECT.ORG`
• [x] Run `fedpkg new-sources $(spectool -S butane.spec | sed 's:.*/::')`
• [x] PR the changes in [Fedora](https://src.fedoraproject.org/rpms/butane)
• [x] Once the PR merges to rawhide, merge rawhide into the other relevant branches (e.g. f39) then push those, for example:
  ```bash
  git checkout rawhide
  git pull --ff-only
  git checkout f39
  git merge --ff-only rawhide
  git push origin f39
  ```
• [x] On each of those branches run `fedpkg build` including rawhide.
• [x] Once the builds have finished, submit them to [bodhi](https://bodhi.fedoraproject.org/updates/new), filling in:
• `butane` for `Packages`
• Selecting the build(s) that just completed, except for the rawhide one (which gets submitted automatically)
• Writing brief release notes like "New upstream release; see release notes at `link to docs/release-notes.md on GH tag`"
• Leave `Update name` blank
• `Type`, `Severity` and `Suggestion` can be left as `unspecified` unless it is a security release. In that case select `security` with the appropriate severity.
• `Stable karma` and `Unstable` karma can be set to `2` and `-1`, respectively.

GitHub release:

• [x] Wait until the Bodhi update shows "Signed :heavy_check_mark:" in the Metadata box.
• [x] Verify that the signing script can fetch the release binaries by running `./signing-ticket.sh test <x.y.z-r> <output-dir>`, where `r` is the Release of the Fedora package without the dist tag (probably `1`)
• [x] Run `./signing-ticket.sh ticket <x.y.z-r>` and paste the output into a [releng ticket](https://pagure.io/releng/new_issue).
• [x] Wait for the ticket to be closed
• [x] Download the artifacts and signatures
• [x] Verify the signatures
• [x] Find the new tag in the [GitHub tag list](https://github.com/coreos/butane/tags) and click the triple dots menu, and create a draft release for it.
• [x] Copy and paste the release notes from `docs/release-notes.md`
• [x] Upload all the release artifacts and their signatures
• [x] Publish the release

Quay release:

• [x] Visit the [Quay tags page](https://quay.io/repository/coreos/butane?tab=tags) and wait for a versioned tag to appear
• [x] Click the gear next to the tag, select "Add New Tag", enter `release`, and confirm
• [x] Visit the [Quay tags page](https://quay.io/repository/coreos/fcct?tab=tags) for the legacy `coreos/fcct` repo and wait for a versioned tag to appear
• [x] Click the gear next to the tag, select "Add New Tag", enter `release`, and confirm

RHCOS packaging for the current RHCOS development release:

• [x] Update the [spec file](https://gitlab.com/redhat/rhel/rpms/butane)
• Bump the `Version`
• Switch the `Release` back to `1%{?dist}`
• Remove any patches obsoleted by the new release
• Run `go-mods-to-bundled-provides.py | sort` while inside of the `butane` directory you ran `./tag_release` from & copy output into spec file in `# Main package provides` section
• Update changelog
• [x] Run `spectool -g -S butane.spec`
• [x] Run `kinit your_account@IPA.REDHAT.COM`
• [x] Run `rhpkg new-sources $(spectool -S butane.spec | sed 's:.*/::')`
• [x] PR the changes
• [x] Get the PR reviewed and merge it
• [x] Update your local repo and run `rhpkg build`
• [x] File ticket similar to [this one](https://issues.redhat.com/browse/ART-3711) to sync the new version to mirror.openshift.com
• [x] Wait until mirror.openshift.com is updated and confirm the new version is correct

CentOS Stream 9 packaging:

• [x] Create a `rebase-c9s-butane` issue in the internal team-operations repo and follow the steps there