dune-release delegate-info version to show the current version as infered by the tool (#495, @samoht)--dev-repo to dune-release and dune-release publish to overwrite the dev-repo field specified in the opam file (#494, @samoht)dune-release not fail in the presence of ~/.dune/bin/dune (which is present when using dune package management)dune-release no longer publishes docs to github pages. Instead, we rely on the docs published under ocaml.org/packages (#499 #500, @v-gb @samoht)opam/ subdirectory. (#466, @Leonidas-from-XIV)dune-release check now attempts to discover and parse the change log, and a new flag --skip-change-log disables this behaviour. (#458, @gridbugs)dune-project. The parser could get confused when opam file generation is used. Now it only considers the first (name X) in the file. (#445, @emillon)dune-release delegate-info and wrap dune-release calls in a script. See #188 for details. (#428, @NathanReb)dune-release expects the opam binary to be version 2.0 at least. (#406, #411, @Leonidas-from-XIV)--skip-lint, --skip-build, --skip-test and --keep-build-dir to the main command (#419, @NathanReb)v as prefix for tags but the project version omits it. Now they share the same URL. (#402, #404, @Leonidas-from-XIV)dune-release supported unannotated tags in a few places already, now it supports using them for creating a release. (#383, @Leonidas-from-XIV)---V command option to be -V (#388, @Leonidas-from-XIV)dune-release on projects that do not use the changelog or have it in a different format. (#381, #383 @Leonidas-from-XIV)dune-release couldn't retrieve a release on GitHub if the tag and project version don't match (e.g. v1.0 vs 1.0). dune-release would in such case believe the release doesn't exist, attempt to create it and subsequently fail. (#387, #395, @Leonidas-from-XIV)--no-auto-open to the default command. It was previously only available for dune-release opam. (#374, @NathanReb)config create subcommand to create a fresh configuration if you don't have one yet (#373, @NathanReb)--local-repo, --remote-repo and --opam-repo options to the default command, they used to be only available for the opam subcommand (#363, @NathanReb)--token option to dune-release publish and dune-release opam commands to specify a github token. This allows dune-release to be called through a Github Actions workflow and use the github token through an environment variable. (#284 #368, @gpetiot @NathanReb)--include-submodules flag to dune-release, dune-release bistro or dune-release distrib (#300, @NathanReb)--draft for dune-release publish and dune-release opam submit commands. (#248, @gpetiot)check to check the prerequisites of dune-release and avoid starting a release process that couldn't be finished (#318, #351, @pitag-ha)--set-upstream to ease any further update of the PR (#350, @gpetiot)opam submit instead of reading the user separately. The information was redundant and could only lead to bugs when unproperly set. (#372, @NathanReb).gitignore, .gitattributes and other such files from the archive. (#299, @NathanReb)dune-release must guess which URI to pass to git push and may guess it wrong. This change allows users to push the tag manually to avoid using that code. (#219, @Julow).git/.hg files and folders from the distrib tarball (#300, @NathanReb)synopsis instead of description (#291, @kit-ty-kate)--user CLI options and configuration field, they were redundant with the remote-repo option and field and could be set unproperly, leading to bugs (#372, @NathanReb)dune-release publish (#276, #302, @pitag-ha)dune-release distrib, it was previously effectively ignored. Now it is required to add a (name <name>) stanza to dune-project. (#327, @lehy)opam submit would look up a config file, even though all the required information was provided on the command line. This would lead to starting the interactive config creation quizz if that file did not exist which made it impossible to use it in a CI for instance. (#373, @NathanReb)opam submit would fail on non-github repositories if the user had no configuration file (#372, @NathanReb)opam submit preventing non-github users to create the opam-repo PR via dune-release. (#359, @NathanReb)opam submit would try to parse the custom URI provided through --distrib-uri as a github repo URI instead of using the dev-repo (#358, @NathanReb)--distrib-uri option in dune-release opam pkg. It used to have lower precedence than the url file written by dune-release publish and therefore made it impossible to overwrite it if needed. (#255, @NathanReb)dune-release opam pkg where you would need the regular dune-release generated archive to be around even though you specified a custom distrib archive file. (#255, @NathanReb)url file before filling the url.src field. This fixes an issue that caused the url.src field to be a multi-line string instead of single line. (#270, @gpetiot).) at the repository from the distrib archive (#298, @NathanReb)dune-release tag cannot guess the project name (#319, @lehy)dune-release distrib (#325, @lehy). Otherwise uncommitted changes to dune-project would be silently ignored by dune-release distrib.publish: Fix the process of inferring user name and repo from the dev repo uri (#348, @pitag-ha)dune-release config subcommand to display and edit the global configuration (#220, @NathanReb).delegate-info to print information needed by external release scripts (#221, @pitag-ha)x-commit-hash field to the opam file when releasing (#224, @gpetiot)tag: improve error and log messages by comparing the provided commit with the commit correspondent to the provided tag (#226, @pitag-ha)dune-release (#231, @pitag-ha)dune-release distrib does not fail when opam's doc field is missing. Do not try to generate nor publish the documentation when opam's doc field is missing. (#235, @gpetiot)publish logs (#171, @hannesm)git command used in publish doc should check DUNE_RELEASE_GIT (even if deprecated) before PATH. (#242, @gpetiot)log subcommand (#196, @gpetiot)opam submit would fail if the opam files had no description (#165, @NathanReb)CHANGES, LICENSE and README (#161, @NathanReb)dune-release logs such as user prompts and informational logs_html folder instead of being published at the root of gh-pages (#157, @NathanReb)dune subst for watermarking. (#147, @NathanReb)CHANGES, LICENSE and README againdune-release publish doc when using multiple packages (#96, @samoht)dune-project files (#104. @samoht)dune-release lint now checks that a description and a synopsis exist in opam2 files (#101, @samoht)git checkout fails in the local opam-repository (#98, @samoht)_html folder when publishing docs on Linux (#94, @anuragsoni and @samoht)Makefile from the distribution archives (#71, @samoht)--tag option to select the release tag (@samoht)--version option to select the release version (@samoht)--keep-v (#70, @samoht)dune-release <OPTIONS> a shorchut to dune-release bistro <OPTIONS> (#75, @samoht)--keep-v and --no-auto-open via options in the config file (#79, @samoht)~/.config/dune/ instead of ~/.dune to match what dune is doing (#27, @samoht)-p <pkg> instead of -n <pkg> to follow dune convention (#30, #42, @samoht)nano if the EDITOR environment variable is not set. (#32, @avsm)odoc creates an _html subdirectory (#34, @samoht)dune-release help delegate) (#37, @samoht)v at the beginning of version numbers in dune-release opam (#40, @let-def)--keep-v option to not drop v at the beginning of version numbers (#6, @samoht)-p <package> to jbuilder (#8, @diml)Distrib.write_subst which could cause an infinite loop (#10, @diml)--dry-run option to avoid side-effects for all commands (@samoht)origin. Instead, just force push the release tag directly to the dev-repo repository (@samoht)opam-publish anymore. Use configuration files stored in ~/.dune to parametrise the publishing workflow. (@samoht)Initial release.
Import some code from topkg.
Astring, Logs, Fpath andBos instead of custom re-implementations;topkg and topkg-care;pkg/pkg.ml file.