Revert "Bump flask from 2.3.3 to 3.1.3"#745
Merged
freakboy3742 merged 1 commit intolektorfrom Feb 21, 2026
Merged
Conversation
This reverts commit 91253b1.
Member
Author
|
... and that didn't work either, because Lektor hasn't been updated in so long that it's being bitten by the Lektor has published an 3.3.13 release that I'm guessing is to address this, which I'm guessing will be picked up by dependabot this week. Until that fix lands, we can't deploy updates to the site. I think all this highlights that getting off Lektor is well overdue. I sure am glad someone did that for us :-) |
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
1 participant
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.
Reverts #744
Although there's a Dependabot security issue tied to this, we're not exposed; and we can't update Flask without also updating Werkzeug (amongst other packages). The publication CI pass tied to this PR failed because of that dependency.
/cc @kattni for visibility