Nathan Rebours
Nathan Rebours
It seems like this might be coming from curly's parsing. Which curl version are you running?
It seems to be something else, could you run it with `--dry-run -vvv` please see if the error still shows up there?
You can probably simply run `dune-release publish distrib --dry-run -vvv` btw, no need to run it all again from scratch!
This might be another instance of a bug we've seen before where upgrading dune-release corrupts the github token. Deleting the token file and trying to re-release should work as dune-release...
Indeed! We'll remove the need for a dune-project file in `2.0.0` as it is only used to determine the tarball name. We'll use the name of the repository in `dev-repo`...
For now unfortunately you'll have to close the PR, delete the github release and the tag and go through the release process again. We do have a plan for supporting...
It might be an error with the token parsing code that we've been running into and that I recently fixed. I'm wrapping up some bug fixes but we should cut...
The tag is for the whole repo and given most tools use tags to determine the version (dune for instance with dune subst) all packages in the same repo have...
Thanks for reporting! Yeah that's probably it, the generated request must be faulty for some reason. Could you please try running the same command with `--dry-run` to see what the...
The issue is indeed that the nbsp isn't properly encoded when generating the json data for the PR opening request.