feat: Add additional /api/v1 routing for endpoints#1511
Merged
Conversation
abbiemery
changed the title
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1511 +/- ##
==========================================
+ Coverage 95.28% 95.30% +0.02%
==========================================
Files 43 43
Lines 3179 3197 +18
==========================================
+ Hits 3029 3047 +18
Misses 150 150 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
ZohebShaikh
approved these changes
Apr 24, 2026
abbiemery
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This adds /api/v1 routing for all current secure endpoints. This leaves both sets of routing usable in in the openapi schema, but marks the ones without the prefix with a deprecation tag. This gives us a step towards having a versioned api while not introducing any breaking changes. Having an api behind a version prefix affords us flexibility going forward to add and migrate to new features with fewer issues.