-
Notifications
You must be signed in to change notification settings - Fork 12
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(javascript): use beta npm org #226
Conversation
鉁旓笍 Deploy Preview for api-clients-automation ready! 馃敤 Explore the source changes: 16e10d1 馃攳 Inspect the deploy log: https://app.netlify.com/sites/api-clients-automation/deploys/6221e4d9fe838800078886ae 馃槑 Browse the preview: https://deploy-preview-226--api-clients-automation.netlify.app |
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.
Is this needed for the release ?
As we don't know for how long we will stay in beta it's easier to iterate directly on the same package (@experimental....) than having to do manual stuff on an other branch |
馃Л What and Why
馃師 JIRA Ticket: https://algolia.atlassian.net/browse/APIC-357
Changes included:
As we don't know how long we will keep the beta open, it's easier for us to iterate on
main
using the beta organization name rather than Algolia.The issue with keeping the
@algolia
npm organization is that it requires me to manually update/rebase a local branch to apply changes.馃И Test
CI :D