We are happy to announce the first release candidate of opam 2.5.0, which boasts a grand total of zero (0) changes compared to 2.5.0~beta1!

We also take this opportunity to announce the release of opam-publish 2.7.1, whose full release notes can be seen here.

Try the new opam 2.5.0 release candidate:

The upgrade instructions are unchanged:

1. Either from binaries: run

For Unix systems

bash -c "sh <(curl -fsSL https://opam.ocaml.org/install.sh) --version 2.5.0~rc1"

or from PowerShell for Windows systems

Invoke-Expression "& { $(Invoke-RestMethod https://opam.ocaml.org/install.ps1) } -Version 2.5.0~rc1"

or download manually from the Github "Releases" page to your PATH.

1. Or from source, manually: see the instructions in the README.

You should then run:

opam init --reinit -ni

Changes in opam-publish 2.7.1

In 2.7.0, opam-publish changed the way user's branch are pushed to their GitHub forks before opening a PR. Previously this was done using a regular SSH key, but it turns out that some people do not have SSH keys or cannot easily use it in automated contexts. To improve this, @filipeom switched the push method to one that uses GitHub's API token that opam-publish already requires. However some problems could appear when upstream opam-repository changes their GitHub Action workflow files as the workflow permission is now sadly required to push to the user's fork.

In 2.7.1, this is fixed by checking that the token has the right scope, as well as advertising this scope when requesting new tokens (#180). More generally, existing tokens with the wrong permissions could be kept (#187), as well as previous setups using SSH (#178).

This release also adds support for the opam 2.5 API (#181, #173).

Please report any issues to the opam bug-tracker or the opam-publish bug-tracker.

Happy hacking!