-
-
Notifications
You must be signed in to change notification settings - Fork 398
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
Backported fixes from branch master to branch 2.2-maintenance #565
Conversation
I think some of the PRs you didn't backport are appropriate for a 2.3 release. Anything that doesn't break existing behavior and just adds a feature is fine.
|
Done. |
I'm not going to review this since it's just backports of things we already merged. Changelog looks good. Not sure if you're keeping this open for more backports, but it's good to go whenever you're ready. |
Yep, no need to review in details. I am confident with the backports being accurate. This was just about knowing what to backport or not. |
#400 says it is not backwards compatible, backporting this broke airflow 1.10.10 setups |
@azmeuk Is it possible to restore |
@kaxil I cannot cut a release myself but hopefully another maintainer will take care of it soon :) |
Thanks 🤞 |
As it was discussed on the discord, I listed the fixes that are present in the master branch and can safely be backported to branch 2.2-maintenance so we could hopefully cut a new 2.* release.
You can see the list of backports in the commit log.
I did not backport:
I did backport #389 but I am not totally confident because of this docstring:
https://github.com/wtforms/wtforms/blob/df892b87365f4a62cab33c98f49ed84660bd18e6/src/wtforms/widgets/core.py#L49-L54