[new release] dune-release (2.0.0) #23986
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CHANGES: ### Added - Adopt the OCaml Code of Conduct (tarides/dune-release#473, @rikusilvola) - Added support for projects that have their OPAM files in the `opam/` subdirectory. (tarides/dune-release#466, @Leonidas-from-XIV) ### Changed - Running `dune-release check` now attempts to discover and parse the change log, and a new flag `--skip-change-log` disables this behaviour. (tarides/dune-release#458, @gridbugs) - List the main package and amount of subpackages when creating the PR to avoid very long package lists in PRs (tarides/dune-release#465, @emillon) ### Fixed - Avoid collision between branch and tag name. Tag detection got confused when branch was named the same as tag. Now it searches only for tag refs, instead of all refs. (tarides/dune-release#452, @3Rafal) - Fix project name detection from `dune-project`. The parser could get confused when opam file generation is used. Now it only considers the first `(name X)` in the file. (tarides/dune-release#445, @emillon) ### Removed - Remove support for delegates. Previous users of this feature should now use `dune-release delegate-info` and wrap dune-release calls in a script. See tarides/dune-release#188 for details. (tarides/dune-release#428, @NathanReb) - Removed support for the OPAM 1.2.2 client. This means `dune-release` expects the `opam` binary to be version 2.0 at least. (tarides/dune-release#406, tarides/dune-release#411, @Leonidas-from-XIV) ### Security
|
Tests failing on macOS is expected. OCaml-CI only recently added those and we need to investigate. However the failures are just about uninitialized git settings so even on macOS it wouldn't affect most normal users who have git set up with their name. |
|
Thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Release dune packages in opam
CHANGES:
Added
opam/subdirectory. (Implement support for OPAM files in
opam/folder tarides/dune-release#466, @Leonidas-from-XIV)Changed
dune-release checknow attempts to discover and parse the changelog, and a new flag
--skip-change-logdisables this behaviour. (Add flag todune-release checkthat attempts to discover and parse the change log tarides/dune-release#458,@gridbugs)
very long package lists in PRs (Use project name for PR title and branch tarides/dune-release#465, @emillon)
Fixed
branch was named the same as tag. Now it searches only for tag refs, instead
of all refs. (Avoid collision between branch and tag name tarides/dune-release#452, @3Rafal)
dune-project. The parser could get confusedwhen opam file generation is used. Now it only considers the first
(name X)in the file. (Fix dune-project name parsing tarides/dune-release#445, @emillon)
Removed
Previous users of this feature should now use
dune-release delegate-infoand wrap dune-release calls in a script. See Replacing delegates tarides/dune-release#188 for details.
(Remove delegates tarides/dune-release#428, @NathanReb)
dune-releaseexpectsthe
opambinary to be version 2.0 at least. (Remove support for opam 1.2 CLI tarides/dune-release#406, Remove support for OPAM 1.2.2 client tarides/dune-release#411,@Leonidas-from-XIV)