This is an automated email from the ASF dual-hosted git repository.

potiuk pushed a commit to branch constraints-1-10
in repository https://gitbox.apache.org/repos/asf/airflow.git


The following commit(s) were added to refs/heads/constraints-1-10 by this push:
     new 1822987  Bumped Flask-OpenID to allow people to upgrade to bridge 
release
1822987 is described below

commit 1822987f88a1fbbaa081bc87b54ad09d57ad56fb
Author: Jarek Potiuk <[email protected]>
AuthorDate: Fri Sep 24 16:53:00 2021 +0200

    Bumped Flask-OpenID to allow people to upgrade to bridge release
    
    Flask-OpenID version 1.2.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.5 cannot be installed with the recent
    setuptools due to 2_to_3 useage. This has been solved by releasing
    1.3.0 and updating constraints for all Airlfow 2 releases, but
    we also should bump it for 1.10.15 to make it seamless for people
    to upgrade to the "bridge" release in case they use an older
    version of Airflow.
---
 constraints-3.5.txt | 2 +-
 constraints-3.6.txt | 2 +-
 constraints-3.7.txt | 2 +-
 constraints-3.8.txt | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/constraints-3.5.txt b/constraints-3.5.txt
index 4090e5a..a86f805 100644
--- a/constraints-3.5.txt
+++ b/constraints-3.5.txt
@@ -7,7 +7,7 @@ Flask-Bcrypt==0.7.1
 Flask-Caching==1.3.3
 Flask-JWT-Extended==3.25.0
 Flask-Login==0.4.1
-Flask-OpenID==1.2.5
+Flask-OpenID==1.3.0
 Flask-SQLAlchemy==2.4.4
 Flask-WTF==0.14.3
 Flask==1.1.2
diff --git a/constraints-3.6.txt b/constraints-3.6.txt
index 8872680..f03a536 100644
--- a/constraints-3.6.txt
+++ b/constraints-3.6.txt
@@ -7,7 +7,7 @@ Flask-Bcrypt==0.7.1
 Flask-Caching==1.3.3
 Flask-JWT-Extended==3.25.0
 Flask-Login==0.4.1
-Flask-OpenID==1.2.5
+Flask-OpenID==1.3.0
 Flask-SQLAlchemy==2.4.4
 Flask-WTF==0.14.3
 Flask==1.1.2
diff --git a/constraints-3.7.txt b/constraints-3.7.txt
index d769c05..4575716 100644
--- a/constraints-3.7.txt
+++ b/constraints-3.7.txt
@@ -7,7 +7,7 @@ Flask-Bcrypt==0.7.1
 Flask-Caching==1.3.3
 Flask-JWT-Extended==3.25.0
 Flask-Login==0.4.1
-Flask-OpenID==1.2.5
+Flask-OpenID==1.3.0
 Flask-SQLAlchemy==2.4.4
 Flask-WTF==0.14.3
 Flask==1.1.2
diff --git a/constraints-3.8.txt b/constraints-3.8.txt
index 065b4e8..ff463f9 100644
--- a/constraints-3.8.txt
+++ b/constraints-3.8.txt
@@ -7,7 +7,7 @@ Flask-Bcrypt==0.7.1
 Flask-Caching==1.3.3
 Flask-JWT-Extended==3.25.0
 Flask-Login==0.4.1
-Flask-OpenID==1.2.5
+Flask-OpenID==1.3.0
 Flask-SQLAlchemy==2.4.4
 Flask-WTF==0.14.3
 Flask==1.1.2

Reply via email to