Fix: Correct X-End-Of-Life-Date header in deprecated_endpoint decorator. Closes #3109#3111
Merged
fgibertoni merged 2 commits intointelowlproject:developfrom Dec 16, 2025
Merged
Conversation
fgibertoni
approved these changes
Dec 16, 2025
Contributor
Author
|
@fgibertoni what am i supposed to do since the test failed, we just changed a value of a variable |
Contributor
|
I think there's another issue, not related to your PR. |
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
3 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.
Fixed a bug in the
deprecated_endpointdecorator where theX-End-Of-Life-Dateresponse header was incorrectly assigned the value ofdeprecation_dateinstead ofend_of_life_date.This was a simple copy-paste error on line 36 of
api_app/decorators.pythat caused API consumers to receive incorrect information about when deprecated endpoints would actually be removed.Impact: API consumers can now properly plan their migrations with accurate deprecation timelines.
Type of change
Checklist
developBlack,Flake,Isort) gave 0 errors.