Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump Flask-SeaSurf to 2.0.0 #60

Merged
merged 1 commit into from
Aug 8, 2024
Merged

Bump Flask-SeaSurf to 2.0.0 #60

merged 1 commit into from
Aug 8, 2024

Conversation

JulienBacquart
Copy link
Contributor

Rather than to a specific GitHub commit.
As Flask-Seasurf on PyPi (v1.1.1) was broken with Flask 3+, and not updated anymore, we had to point in the mtw_requirements.txt to a specific commit on GitHub instead.
The commit was merged for the 2.0.0 release and doesn't exist anymore, so pointing to the specific commit break the pip process now.

Rather than to a specific GitHub commit.
As Flask-Seasurf on PyPi (v1.1.1) was broken with Flask 3+, and not
updated anymore, we had to point in the mtw_requirements.txt to
a specific commit on GitHub instead.
The commit was merged for the 2.0.0 release and doesn't exist anymore,
so pointing to the specific commit break the pip process now.
@filak
Copy link
Owner

filak commented Aug 7, 2024

Yes, I will test tomorrow if the new version of Flask-SeaSurf works and then merge this PR.

Copy link
Owner

@filak filak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

@filak filak merged commit 7b20d9e into filak:master Aug 8, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants