hatch publish exits with zero exit code when artifacts already exist

[zanieb]

My release workflow runs hatch publish

When publishing the release for the 0.0.36 tag, I got the output:

$ hatch publish
dist/ruff_lsp-0.0.35.tar.gz ... already exists
dist/ruff_lsp-0.0.35-py3-none-any.whl ... already exists

Source

This is because we forgot to bump the version of the library when publishing the new release. The release workflow succeeded because hatch publish does not exit with a non-zero exit code. Thus the new release was not uploaded to PyPI but we did not get notified of a failed release workflow.

I expect hatch publish to exit with a non-zero exit code if the artifacts already exist — or for it to include an option to do so. I looked through the docs and couldn't find anything about this. I did find a previous issue at #91 which suggests that this behavior used to be available?

Related: python-poetry/poetry#3304

Thanks!