Brian Rutledge

FWIW, there was some discussion about this in https://github.com/pypa/twine/issues/496.

FYI, I did some investigation, and it's not obvious how to use multiple project API tokens with twine and keyring: https://github.com/pypa/twine/issues/565.

Checking in on the desired outcome of this issue. I've been passively tracking issues related to twine and credentials (most recently ). My sense is that the documentation around `.pypirc`,...

Related: https://github.com/pypa/packaging.python.org/issues/628 and https://github.com/pypa/twine/issues/496 re: project-scoped API tokens. The suggestion seems to be to configure "proxy" repositories for each project, with distinct tokens. I haven't investigated if/how those are supported...

> I haven't investigated if/how those are supported by twine when using keyring. I did some investigation, and it's not obvious how to use multiple project API tokens with twine...

Is the fix to remove `--skip-existing` here? https://github.com/cdklabs/publib/blob/aa230620b5037de7e9b125fd0cd4e34960854858/bin/publib-pypi#L39-L40 I tried to work around this by running `pip install 'twine

> We can also try and rebuild the skip existing support in publib. Something like this would be my vote. It seems like Twine and `--skip-existing` is an implementation detail...

@mrgrain https://github.com/projen/projen/issues/4352#issuecomment-3401111273 says this has been resolved. Can you link to where/how that was done? Should this issue be closed?

> What would help is a community review and verification @mrgrain Something that would help with that is an alpha release of projen that includes this PR. IIRC, it's hard/impossible...