Skip to content
Discussion options

You must be logged in to vote

Hi @ykanchugantl in development we started returning 410 when using deprecated endpoints to push us to use only non-deprecated ones, but it'd still work in production (which is what you are seeing). At the same time, that endpoint was deprecated since v4.17.0 but we believe it was due to a copy&paste "accident" so we just un-deprecated it 2 days ago: #10083 (meaning it should be usable from main)

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by gastonfournier
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants