View all changes

2.7.1

We announce the release of opam-publish 2.7.1, whose full release notes can be seen here.

Changes in opam-publish 2.7.1

In 2.7.0, opam-publish changed the way user’s branches are pushed to their GitHub forks before opening a PR, switching from using SSH keys to using the GitHub API token that opam-publish already requires.

2.7.1 fixes a couple of bugs related to that where opam-publish stopped working if the GitHub Action workflow files of upstream opam-repository are changed, owing to the way GitHub token permissions work. Thanks to @filipeom both for the original contribution in 2.7.0 and for subsequent work on it in 2.7.1.

Read our blog post for more details.

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

See full changelog
  • Advertise the need, and check, for the workflow scope for github personal access tokens [#184 @kit-ty-kate - fix #180]
  • Enforce the git remote used to push branches to users' fork to be used instead of the SSH method, for users migrating from versions of opam-publish prior to 2.7.0 [#179 @filipeom - fix #178]
  • Avoid potential previously used tokens with the wrong permissions to be used instead of the new one [#179 @filipeom - fix #187]
  • Add support for the opam 2.5 API [#181 #173 @kit-ty-kate]