search

wooyek / flask-social-blueprint

An OAuth based authentication blueprint for flask. Easy to extend and override.
MIT License
83 stars 29 forks source link

Update flask-wtf to 0.14.1 #56

Closed pyup-bot closed 7 years ago

pyup-bot commented 7 years ago

There's a new version of Flask-WTF available. You are currently using 0.13.1. I have updated it to 0.14.1

These links might come in handy: PyPI | Changelog | Repo | Docs

Changelog

0.14.1

Released 2017-01-10

  • Fix bug where the file validators would incorrectly identify an empty file as valid data. (276, 277)

    • FileField is no longer deprecated. The data is checked during processing and only set if it's a valid file.
    • has_file is deprecated; it's now equivalent to bool(field.data).
    • FileRequired and FileAllowed work with both the Flask-WTF and WTForms FileField classes.
    • The Optional validator now works with FileField.

.. _276: https://github.com/lepture/flask-wtf/issues/276 .. _277: https://github.com/lepture/flask-wtf/pull/277

0.14

Released 2017-01-06

  • Use itsdangerous to sign CSRF tokens and check expiration instead of doing it ourselves. (264_)

    • All tokens are URL safe, removing the url_safe parameter from generate_csrf. (206_)
    • All tokens store a timestamp, which is checked in validate_csrf. The time_limit parameter of generate_csrf is removed.

  • Remove the app attribute from CsrfProtect, use current_app. (264_)

  • CsrfProtect protects the DELETE method by default. (264_)

  • The same CSRF token is generated for the lifetime of a request. It is exposed as request.csrf_token for use during testing. (227, 264)

  • CsrfProtect.error_handler is deprecated. (264_)

    • Handlers that return a response work in addition to those that raise an error. The behavior was not clear in previous docs.
    • (200, 209, 243, 252)

  • Use Form.Meta instead of deprecated SecureForm for CSRF (and everything else). (216, 271)

    • csrf_enabled parameter is still recognized but deprecated. All other attributes and methods from SecureForm are removed. (271_)

  • Provide WTF_CSRF_FIELD_NAME to configure the name of the CSRF token. (271_)

  • validate_csrf raises wtforms.ValidationError with specific messages instead of returning True or False. This breaks anything that was calling the method directly. (239, 271)

    • CSRF errors are logged as well as raised. (239_)

  • CsrfProtect is renamed to CSRFProtect. A deprecation warning is issued when using the old name. CsrfError is renamed to CSRFError without deprecation. (271_)

  • FileField is deprecated because it no longer provides functionality over the provided validators. Use wtforms.FileField directly. (272_)

.. 200: https://github.com/lepture/flask-wtf/issues/200 .. 209: https://github.com/lepture/flask-wtf/pull/209 .. 216: https://github.com/lepture/flask-wtf/issues/216 .. 227: https://github.com/lepture/flask-wtf/issues/227 .. 239: https://github.com/lepture/flask-wtf/issues/239 .. 243: https://github.com/lepture/flask-wtf/pull/243 .. 252: https://github.com/lepture/flask-wtf/pull/252 .. 264: https://github.com/lepture/flask-wtf/pull/264 .. 271: https://github.com/lepture/flask-wtf/pull/271 .. 272: https://github.com/lepture/flask-wtf/pull/272

Got merge conflicts? Close this PR and delete the branch. I'll create a new PR for you.

Happy merging! 🤖

pyup-bot commented 7 years ago

Closing this in favor of #58