I can’t find anything in
dune-release opam submit --help except:
The change log to use. If absent, provided by the package
I can’t see any key for
mypackage.opam that looks like a changelog in opam - Manual so I guess it means the
description value? not sure what the content needs to look like to be recognised as a changelog though
actually… looking at https://github.com/ocamllabs/dune-release/blob/71bdccf4765939c29cfd85e17df90a87fd1c1182/lib/pkg.ml#L66 it seems by “package description” it really just means “files in the project repo”
In case there is some way via the package description I tried creating a
so that Dune will add this key to the generated .opam file
but when I
dune-release distrib I see:
[-] Performing lint for package spectrum in _build/mypackage-8d10ec7
[ OK ] File README is present.
[ OK ] File LICENSE is present.
[FAIL] File CHANGES is missing.
[ OK ] File opam is present.
[FAIL] lint opam file mypackage.opam:
opam lint -s messages:
error 3: File format error in 'changelog' at line 39, column 0: Invalid field changelog
and if I then
dune-release opam pkg and
dune-release opam submit I still get:
dune-release: [ERROR] No change log specified in the package description.
Finally I got rid of the opam template and created a dummy
CHANGES file that just said “see git commit history”
That linted ok but I got:
dune-release opam submit
dune-release: [ERROR] ./CHANGES: Could not parse change log.
So it seems like I have to have a
CHANGES file formatted in the way that