feat: 🗑️ Redirect deprecated /api requests to /api/2014
#672
Conversation
This file contains 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
bagelbits
reviewed
Feb 22, 2025
bagelbits
approved these changes
Feb 22, 2025
|
🎉 This PR is included in version 3.13.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
What does this do?
Adds a permanent redirect (HTTP 301) to
/api/*routes, pointing to the corresponding/api/2014/*route.How was it tested?
Manual testing in local docker container. Unit & integration tests updated to ensure 301 status code and
res.redirectis called when appropriate.Is there a Github issue this is resolving?
No.
Was any impacted documentation updated to reflect this change?
Yes. Replaced
/apipath inswagger.ymlwith/api/2014.Here's a fun image for your troubles