-
Notifications
You must be signed in to change notification settings - Fork 339
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
Introduce temporary package version restrictions #579
Introduce temporary package version restrictions #579
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #579 +/- ##
=======================================
Coverage 96.45% 96.45%
=======================================
Files 20 20
Lines 2733 2733
=======================================
Hits 2636 2636
Misses 97 97 ☔ View full report in Codecov by Sentry. |
Bench test fails because install is broken on master, so that can safely be ignored! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Is there an issue with jsonschema==4.19.1? This restriction is causing conflicts in our environment because other tools require 4.19.1. |
@brianpaden289 There is an open issue and PR for jsonschema related stuff. It looks like part of the package we use either has been removed or is going to be removed. I just haven't had a chance to look at it yet unfortunately! See #560 |
This PR introduces a temporary restriction on flask, werkzeug and jsonschema packages until we can get everything updated.
It was my intention to temporarily point the pytest-flask installation to a fork that included the 3.0.0 fixes until they are merged upstream. However, the pipeline installs via setuptools and the
pip()
function insetup.py
strips out pip git checkout links.