-
-
Notifications
You must be signed in to change notification settings - Fork 149
Feature: cut over to v2 API #508
Comments
Would love to help with that 😃 Need to find my mark again 😅 |
Sure thing! Should be pretty simple for the hot repo since there's not much that's changing besides We won't merge it until we've cut in the new api from the Ping me if you have questions! |
Hey @takanome-dev - We're getting really close to doing the v2 cutover: any progress here? I may reassign this to me if you haven't started working on it yet since this was originally intended to be core team work and we're moving pretty fast on making this v1 --> v2 transition happen. |
Hey @jpmcb, I haven't started it yet. I was planning to tackle it over the weekend, as I thought there was still some time before v2 is ready. However, if it's time-sensitive for the core team, please go ahead and reassign. Apologies for any inconvenience, and thanks for the understanding! |
No worries! I'll assign myself: we ended up moving much faster on this than I anticipated. Thanks for grabbing this tho! |
Re-opening since we'll also want to track this going into production next week. |
Closed by: #510 |
Type of feature
🍕 Feature
Current behavior
Related: https://github.com/open-sauced/api/issues/478
Suggested solution
The v1 API is being deprecated: we should cut over to the v2 API and tee up changes ready for when the v1 API goes down
Additional context
No response
Code of Conduct
Contributing Docs
The text was updated successfully, but these errors were encountered: