Skip to content

[DRAFT] Add script for cutting releases - #15558

Draft
shonfeder wants to merge 1 commit into
mainfrom
shonfeder/release-cut-script
Draft

[DRAFT] Add script for cutting releases#15558
shonfeder wants to merge 1 commit into
mainfrom
shonfeder/release-cut-script

Conversation

@shonfeder

Copy link
Copy Markdown
Member

Description

A bash script to automate the process of cutting releases. It still has some missing edge cases and I'm not confident in it's ability run correctly in all cases. I will be doing more testing on my fork before requesting reviews.

Related Issue and Motivation

Fixes #14281

Checklist

  • Tests added, if applicable.
  • Change log entry added for any user-facing changes.
  • Documentation added for any user-facing changes.

Signed-off-by: Shon Feder <shon.feder@gmail.com>
@shonfeder shonfeder changed the title [DRAFT]] Add script for cutting releases [DRAFT] Add script for cutting releases Jul 19, 2026
Comment on lines +21 to +31
# - NB. To stage a release against forks, dune-release reads the following from
# the environment; they pass through 'make opam-release' unchanged:
# - DUNE_RELEASE_DEV_REPO the dune fork the release/tag/tarball goes to
# (a plain git URL, e.g. https://..., not git+https)
# - DUNE_RELEASE_OPAM_REPO the opam-repository the package PR is opened into
# (owner/repo form)
# - DUNE_RELEASE_REMOTE_REPO your fork of opam-repository to push the PR from
# (a git URL, e.g. git@github.com:you/opam-repository.git)
# - DUNE_RELEASE_LOCAL_REPO path to a local clone of that opam-repository fork
# Set DUNE_REMOTE to the matching dune fork remote so the release branch and
# changelog commit are pushed there too.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In my attempt to test this locally against my personal forks today, I found that this is actually insufficient for testing locally, because despite having export DUNE_RELEASE_DEV_REPO=https://github.com/shonfeder/dune.git, dune-release still tried to push the release to the main repo, based on the opam file configuration. I am not sure yet whether this was due to a configuration error on my part, or some unexpected behavior from dune-release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Automate cutting releases

1 participant