mirror of
https://github.com/hasura/graphql-engine.git
synced 2024-12-17 04:24:35 +03:00
adca95a78d
Rather than a homebrewed approach, we can use `make` to figure out when it's necessary to regenerate our venv. This Makefile will regenerate _requirements.txt_ from _requirements-top-level.txt_ when the latter is changed. It will also regenerate the venv when _requirements.txt_ is changed (i.e. changes are pulled, or it's regenerated as described above). `make` uses file/directory timestamps to figure out what to rebuild. This is probably more reliable than expecting people to update a version number whenever they change a file. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5152 GitOrigin-RevId: 24b27d49bf6c4ba1d57ac38ea38ae278216c6d66
19 lines
468 B
Plaintext
19 lines
468 B
Plaintext
# Direct dependencies go here.
|
|
# Regenerate requirements.txt by running `make` in this directory.
|
|
|
|
croniter
|
|
cryptography == 3.* # later versions require Rust support
|
|
graphene == 2.* # v3 has changed the API
|
|
graphql-core
|
|
jsondiff
|
|
psycopg2-binary
|
|
PyJWT == 2.3.* # v2.4 disallows the key format we use
|
|
pytest == 6.2.5
|
|
pytest-xdist
|
|
PyYAML
|
|
redis
|
|
requests
|
|
ruamel.yaml
|
|
sqlalchemy
|
|
websocket-client == 0.56.0 # 0.58.0 and above changed the function signatures of callbacks
|