graphql-engine/server/tests-py/requirements-top-level.txt
Samir Talwar 89eafb1589 server: Re-freeze tests-py/requirements.txt.
I tried re-freezing _server/tests-py/requirements-top-level.txt_
recently, and discovered that it caused the tests to fail.

This pins a couple of dependencies so that we can safely re-freeze.
Specifically:

- `cryptography` is pinned at v3.*
- `graphene` is pinned at v2.*
- `PyJWT` is pinned at v2.3.*
- `websocket-client` is pinned at v0.56.0 (this was done in
  _requirements.txt_ already, but that file is supposed to be
  regenerated)

Upgrading `SQLAlchemy` required changing PostgreSQL URLs to use
"postgresql://" as the URL scheme, not "postgres://".

Updating `ruamel.yaml` caused a few tests to fail as we are passing
`ruamel.yaml.scalarstring.LiteralScalarString` values as header values.
This is fixed by explicitly converting header values to strings.

PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5120
GitOrigin-RevId: 9c12a3013c3d1f23dddbe781037663838b23f6f5
2022-07-22 10:25:33 +00:00

17 lines
441 B
Plaintext

# IF YOU CHANGE THIS PLEASE INCREMENT DEVSH_VERSION in `scripts/dev.sh`
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