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
When I run the command above it says there is no https:// or http:// schema on the URL.
I'm using the .pypirc file.
The strange thing is that hatch publish --repo test dist/* works fine.
BTW, there is a schema for both pypi and testpypi before the URL in the .pypirc file.
Also, twine upload --repository pypi dist/* works fine.
$ hatch --version
Hatch, version 1.14.0
The text was updated successfully, but these errors were encountered:
hatch only references .pypirc to attempt to source the username and password for a repository that it knows about. Use the [publish.index.repos.<REPO>] table to configure available registries.
If the repo name (as configured in the hatch repos table) matches an entry in .pypircOR the repo url matches any entry in .pypirc, the username and password will be applied. Your test registry is working because the url for testpypi and hatch's default test repository match.
If the URL for your pypi entry in your .pypirc is https://upload.pypi.org/legacy/, use the default hatch publishing repo main (or just omit the --repo all together): hatch publish --repo main dist/*
When I run the command above it says there is no https:// or http:// schema on the URL.
I'm using the
.pypirc
file.The strange thing is that
hatch publish --repo test dist/*
works fine.BTW, there is a schema for both
pypi
andtestpypi
before the URL in the.pypirc
file.Also,
twine upload --repository pypi dist/*
works fine.$ hatch --version
Hatch, version 1.14.0
The text was updated successfully, but these errors were encountered: