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 and Werkzeug versions #3138

Open
ndrezn opened this issue Jan 29, 2025 · 2 comments
Open

Bump Flask and Werkzeug versions #3138

ndrezn opened this issue Jan 29, 2025 · 2 comments
Assignees
Labels
infrastructure build process etc. P2 considered for next cycle

Comments

@ndrezn
Copy link
Member

ndrezn commented Jan 29, 2025

We pin flask and werkzeug to older (3.0.6 / 3.0.3) versions. We should upgrade these.

We'll need to ensure compatibility across our ecosystem (OSS and Enterprise libraries). This is likely not something for 3.0 but worth considering.

@ndrezn ndrezn marked this as a duplicate of #3136 Jan 29, 2025
@gvwilson gvwilson changed the title [Feature Request] Bump Flask and Werkzeug versions Bump Flask and Werkzeug versions Feb 3, 2025
@gvwilson gvwilson added infrastructure build process etc. P2 considered for next cycle labels Feb 3, 2025
@nhoover
Copy link

nhoover commented Feb 19, 2025

Would be really nice if this could be included in 3.0

@ndrezn
Copy link
Member Author

ndrezn commented Mar 11, 2025

This issue was encountered during a Dash Enterprise trial.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
infrastructure build process etc. P2 considered for next cycle
Projects
None yet
Development

No branches or pull requests

4 participants