You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When releasing multiple packages at once, dune-release seems to pick an arbitrary order for the package names in the release. For instance:
[new release] alcotest-lwt, alcotest, alcotest-async and alcotest-mirage (1.2.0)
Open • CraigFe wants to merge 1 commit into master from release-alcotest-1.2.0
Lwt-based helpers for Alcotest
• Project page: https://github.com/mirage/alcotest
• Documentation: https://mirage.github.io/alcotest
##### CHANGES:
When it does this, it constructs the PR description from the first package in the list. It'd be good to have some way of giving dune-release either a file from which to take the description (à la hubpull-request -F <FILE>), or to tell it that one particular package is the "canonical" one and should always appear first. (The latter would suffice for all of the projects I regularly release.)
The text was updated successfully, but these errors were encountered:
After some further thought, it also seems fine for dune-release to just not try to find a package description when there are multiple in the repository.
When releasing multiple packages at once,
dune-release
seems to pick an arbitrary order for the package names in the release. For instance:When it does this, it constructs the PR description from the first package in the list. It'd be good to have some way of giving
dune-release
either a file from which to take the description (à lahub
pull-request -F <FILE>
), or to tell it that one particular package is the "canonical" one and should always appear first. (The latter would suffice for all of the projects I regularly release.)The text was updated successfully, but these errors were encountered: