hatch release: --strict flag is misleading?

[karlicoss]

At the moment --help for hatch release says: -s, --strict Aborts if a distribution already exists..

I expected it to exit with non-zero code if the package already existed.
However, behaviour seems to be the opposite of what I expect:

$ hatch release 
Uploading distributions to https://upload.pypi.org/legacy/
  Skipping cachew-0.6-py2.py3-none-any.whl because it appears to already exist
(exit code 0)
$ hatch release --strict 
Uploading cachew-0.6-py2.py3-none-any.whl
100%
(exit code 0)

So instead of aborting, --strict have forced uploading.
It seems that the option simply forwards to --skip-existing of twine upload, which means:

--skip-existing       Continue uploading files if one already exists. 

Should the --strict flag do exactly the opposite? Also --abort normally implies non-zero exit code, I think; is hatch meant to implement this logic?

Happy to open a PR fix it, just not sure what was the original intent. Thanks.

[ofek]

Hatch has been rewritten from scratch and now no longer uses twine so no more --strict, see https://ofek.dev/hatch/latest/publish/