Steps to follow for each release

Finalise opam code for release

• update version in opam files, configure.ac
• run make configure to regenerate ./configure [checked by github actions]
• update copyright headers
• run make tests, opam-rt [checked by github actions]
• update the CHANGE file: take master_changes.md content to fill it

Github release

[ once bump version & changes PRs merged ]

• tag the release (git tag -am 2.2.0 2.2.0; git push origin 2.2.0)
• /!\ Once the tag pushed, it can be updated [different commit] only in case of severe issue
• create a release (or prerelease if intermediate release) draft on github based on your tag (https://github.com/ocaml/opam/releases/new)
• fetch locally the tag
• generate opam artifacts, using release/release.sh <tag> from a macOS/arm64 machine, it requires to have Docker and QEMU installed (see below device requirements)
• generate the signatures using release/sign.sh <tag>
• add releases notes (content of master_changes.md) in the release draft
• upload everything from release/out/<tag>
• finalise the release (publish)

Publish the release

• add hashes in install.sh (and check signatures)
• publish opam packages in opam-repository
• update versions (and messages, if necessary) in https://github.com/ocaml/opam-repository/blob/master/repo

Announce!

• a blog entry in opam.ocaml.org
• a announcement in discuss.ocaml.org

After release

• Bump the version with a ~dev at the end (e.g. 2.2.0~alpha~dev)
• Check if reftests needs an update
• Bring the changes to the changelog (CHANGES) from the branch of the release to the master branch

On a release candidate

• create a branch to a x.y for rc's and the final release
• remove shell/install.sh

---

Device requirements

• Mac M1
• installed: git, gpg
• opam repo with the tag fetched
• Have the secret key available
• Launch docker using the Docker GUI macOS app