Streamlining the release of dune packages to opam
CHANGES:
_html
folder instead of being published at the
root of gh-pages
(#157, @NathanReb)CHANGES:
dune subst
for watermarking. (#147, @NathanReb)CHANGES
, LICENSE
and README
againCHANGES:
CHANGES:
dune-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)CHANGES:
CHANGES:
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)CHANGES:
~/.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)CHANGES:
--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.