Moving v3 docs below v2/v1 #1474
Merged
Conversation
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
Per Slack convo w/ RL.
Contributor
|
I am still seeing v3 at the top, will take a quick look at this: |
JamesDemeryNava
approved these changes
Jan 29, 2026
Contributor
JamesDemeryNava
left a comment
JamesDemeryNava
left a comment
There was a problem hiding this comment.
Looks good to me!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 moves v3 endpoint descriptions below v2/v1, as they are not yet in production.
JIRA Ticket:
BB2-4489
What Does This PR Do?
See above.
What Should Reviewers Watch For?
We should make sure this renders correctly in the new order.
Validation
Observational.
What Security Implications Does This PR Have?
None.
Any Migrations?
No migrations.