This is a rough first pass at updating the package name on PyPI to pinecone. It doesn't attempt preserve the prior package workflow -- we may want to continue to publish to both for some period of time? We may also want to update the publishing workflow first, then doc changes later.
Solution
Updated Readmes, inline docs, and github workflows to support pinecone instead of pinecone-client
Type of Change
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[X] This change requires a documentation update
[X] Infrastructure change (CI configs, etc)
[ ] Non-code change (docs, etc)
[X] None of the above: (explain here): Package name update
Test Plan
Does it publish to the new namespace?
How much work do we have to do to help users migrate from pinecone-client -- i.e. are there any automatic redirects, or is this a manual deprecation?
Per https://github.com/pypi/support/issues/2432#issuecomment-2066632560 -- we have the
pinecone
package name on PyPIProblem
This is a rough first pass at updating the package name on PyPI to
pinecone
. It doesn't attempt preserve the prior package workflow -- we may want to continue to publish to both for some period of time? We may also want to update the publishing workflow first, then doc changes later.Solution
Updated Readmes, inline docs, and github workflows to support
pinecone
instead ofpinecone-client
Type of Change
Test Plan
pinecone-client
-- i.e. are there any automatic redirects, or is this a manual deprecation?