Hi there, Although the state of build and release tools has contiuously improved over the years (and I deeply thank all people involved in this transition), in particular regarding the simplification of steps to perform, I still find myself having trouble releasing software in Opam. So I’d like to …

Incidentally, I finished rewriting my packages using dune, dune-release, and OPAM 2.0 just yesterday. dune-release behaves pretty much exactly like topkg on the command line. You can thus follow the usual process as outlined in my mentioned post and replace every occurence of topkg with dune-relea…

I’ve just been contacted by the Thomas Gazagnaire (the dune-release maintainer) to discuss the recent problems. Strangely, when trying to replicate the problems to provide more details, it turned out that both the *.descr linting issue as well as the documentation publication issue have disappeared…

@grayswandyr Submitting a pull request will always create a new branch in your local OPAM repository. Just check out this branch if you need to manually make changes. I don’t actually know what happens if you use dune-release again to submit updates to the same package version. I’ll probably try …

Indeed, it’s not clear whether dune-release can simply update a PR branch. Anyway I guess this would be restricted to updating the OPAM file. Because, in your process, what do you do if the OPAM checks, after submission, tell you that the version of your repo you (git) tagged is buggy? You are forc…

If you re-submit an already existing PR, it will just update the PR (basically it will force-push the new change to your branch). The branch name is of the form release-<name>-<version> so as long as you don’t change the version it will keep pushing on the same branch and update the existing PR.

Also, the expected workflow is supposed to be: add a tag in your Git repo. This should be done via dune-release tag [tag-name] and/or manually. If you don’t supply a tag name, it will look into your change file to guess something. run dune-release. This is very similar to topkg bistro but it s…

Thanks for your answers. @samoht is dune-release able to pas through proxies? At a moment, it was apparently considered that the package name field should not appear in opam files prior to submission: what is the policy for dune-release?

[image] grayswandyr: At a moment, it was apparently considered that the package name field should not appear in opam files prior to submission I think it is generally unusual to have a package name inside the opam file. The usual way is to name it packagename.opam in your repository, which al…

[image] grayswandyr: @samoht is dune-release able to pas through proxies? It’s currently shelling out to curl and git directly, so if if your proxy is configured properly to work with these, it should work. (note: using curl directly is actually very fragile and might change in the future). …

Packaging process

Ecosystem

grayswandyr October 26, 2018, 2:48pm 3

Thanks for the heads up. I indeed met a bug with documentation.
How do you proceed, if the PR is refused by an automatic CI test, to update this very PR without creating a new tag?

Topic		Replies	Views
How do I fix a broken opam submission with dune-release? Learning opam , dune-release	6	799	November 19, 2020
How to use dune-release distrib with 3 packages? Ecosystem dune-release	3	636	December 7, 2020
Dune-release: version 1.4.0 released Ecosystem opam , announce , release , dune , dune-release	0	1008	July 16, 2020
Best way to publish opam package Learning opam	33	3624	May 2, 2024
Dune-release workflow when CI fails Ecosystem	2	464	August 30, 2021

Packaging process

Related topics