-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[PACK] Rename cloud SDK package name when importing (#344) #71
Conversation
Hey @Mildophin! You can't actually rename the PyPI registry, a new one under Nonetheless, here are is a template with a few steps you can follow to mitigate the impact of this change: https://github.com/simonw/pypi-rename |
ca7bb39
to
eef2ca4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM for the most part. Two small things I'm wondering about:
- Did we create a new pypi package yet ? Do we need to set new credentials for the github actions ?
- We still need to rename the github repo, do you have a clear plan for that ?
6844e74
to
7b0ef16
Compare
93447db
to
9a6af0e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple minor things to fix.
Also should we bump the minor on this? Or is it ok since we're backwards compatible?
As it is backward compatible if we follow the rules it seems fine to declare it as a patch and actually as your previous commit is a breaking change, the 0.2.1 makes sense for my MR |
9a6af0e
to
ad7ac55
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, we'll rename the github repo right after this is merged
Let me know if you have an idea about how to change the lib name on pypi !