Between now and 25th of September, we'll be deprecating user-based repositories and accounts.
If you have a user account, with repositories, we'll be performing the following actions for you:
If you have a user account, but with no repositories:
As part of this process, we'll put the following restrictions in place:
Some of these steps will happen earlier than 25th of September (e.g. preventing the creation of new repositories for users). You're also free to migrate yourself earlier, at any point.
Not at all! This is a user-focused change, and orgs are not affected.
Only if you use your username + password (or API key) to download packages. As part of the migration, your username will be changed slightly, so you're using this, you'll need to adapt your client-side configuration.
Other than that, we've designed the migration process so that the majority of your client-side tools and integrations will remain the same. The API key you were using will be the same (you'll still authenticate as your user), and any push configuration will use the same account slug/username.
The repository configurations will also remain the same, so you don't need to update/change settings, entitlement tokens, packages, etc.
For example, if your username was cloudsmyths and you were doing the following to upload a Debian package, it will still work the same:
cloudsmith push deb cloudsmyths/production/ubuntu/xenial/ cloudsmyths-1.2.5.deb
Your new username will be something like cloudsmyths-owner. So the only impact/change that might be necessary is if you are downloading packages using your username + password. If so, you'll need to update your username to match.
You'll be able to rename both your user and your organisation after the migration, in the situation you're not happy with our renames.
This is part of our vision for being even more customer-obsessed, by focusing on the team aspects of the Cloudsmith experience. Individual users are, and always be, an integral part of our service; but the best of package management is built on collaboration with others. So by changing the focus of accounts to org-only, we hope to build even greater value for teams around the world. Other than that, this shouldn't impact how you interact with Cloudsmith. You'll just as easily be able to create an organisation with one member. :-)
Ultimately: Don't Panic! No (or little) action is necessary. You'll still be signing in as a user as you've always done.
For any questions or concerns, please contact us; we'll be happy to help, and put your mind at ease!
Thanks for subscribing!
Check your inbox to verify your email