stevebleazard

I'm getting a very similar issue. Having deleted release files and tags. I built the latest master and ran ``` ../dune-release/_build/default/bin/main.exe publish --verbosity=debug distrib 2>&1 | tee err ``` The...

To make sure everything was clean I deleted the token, created a new repo (with the same content except I updated the .opam file) and used the following steps: -...

After re-creating the test repo and re-running I get the 422 error. In this case I tagged with a version of 1.0.0 ``` ../dune-release/_build/default/bin/main.exe publish distrib --verbosity=debug main.exe: [INFO] dune-release...

It looks like github has weird behaviour when the name contains a dot, So when I deployed to jsonxt.test, it appeared in the jsonxt.pre-release repo, possible as well as jsonxt.test....

The issue appears to be caused by dots in the repo name. Removing the dots and everything worked as expected

Let me run some tests and update the ticket, I'm not even sure this is a dune-release issue as when I was testing with jsonxt.test some of the debug output...

Testing - Cloned and built the master branch of dune-release - Created a new testrepo.test - Added files to the repo and commit/pushed - tag release: ../dune-release/_build/install/default/bin/dune-release tag - build...

> > > FYI @stevebleazard there's your token in that trace. I would advise revoking it (if github's token scrubbing didn't already find it) Thanks, I've been revoking the tokens...

Confusion on my part, I have re-opened