-
Notifications
You must be signed in to change notification settings - Fork 60
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
Cosmos JS repo is moving #411
Comments
FYI - any unresolved bug reports will be closed as part of this migration. We usually advise creating a new bug report rather than commenting on an old one. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days |
We're moving to the https://github.com/Azure/azure-sdk-for-js repo! 🎉🎉🎉
V3 🧀🚚
The contents of master are being moved to azure-sdk-for-js.
V3 issues and feature requests will move to azure-sdk-for-js. Any new issues opened on this repo that are V3 bugs or feature requests will be moved to the azure-sdk-for-js repo.
Once we've switched development to the new repo, we'll update the readme to make this clear.
V2 🧊
For the time being V2 code and issues will stay in this repo. If you're not sure if it's a V2/V3 issue, you can use the azure-sdk-for-js and we'll manage it there.
Once V2 is end of life'd (not announced yet; 1 year's notice will be given), this repo will be archived.
The text was updated successfully, but these errors were encountered: