You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ git clone https://github.com/janestreet/spawn.git
$ cd spawn
$ dune-release distrib
[...]
<failure because jbuilder picks up the wrong workspace root>
I think all the calls to jbuilder should have -p <package> to make sure they are reproducible, i.e.:
they don't read the user configuration file
the root is wherever jbuilder is started
...
The text was updated successfully, but these errors were encountered:
CHANGES:
- Remove opam lint warnings for 1.2 files (tarides/dune-release#2, @samoht)
- Add a `--keep-v` option to not drop `v` at the beginning of version
numbers (tarides/dune-release#6, @samoht)
- Pass `-p <package>` to jbuilder (tarides/dune-release#8, @diml)
- Fix a bug in `Distrib.write_subst` which could cause an infinite loop
(tarides/dune-release#10, @diml)
- Add a `--dry-run` option to avoid side-effects for all commands (@samoht)
- Rewrite issues numbers in changelog to point to the right repository
(tarides/dune-release#13, @samoht)
- Stop force pushing tags to `origin`. Instead, just force push the release
tag directly to the `dev-repo` repository (@samoht)
- Fix publishing distribution when the the tag to publish is not the repository
HEAD (tarides/dune-release#4, @samoht)
- Do not depend on `opam-publish` anymore. Use configuration files stored
in `~/.dune` to parametrise the publishing workflow. (@samoht)
Step to reproduce:
I think all the calls to jbuilder should have
-p <package>
to make sure they are reproducible, i.e.:The text was updated successfully, but these errors were encountered: