Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/requirements
History
Mateusz Mandera a1fa2a8cf5 scim: Upgrade to django-scim2 0.17.1. 
The new release adds the commit:
20ac22b96d

Which allows us to get rid of the entire ugly override that was needed
to do this commit's job in our code. What we do here in this commit:
* Use django-scim2 0.17.1
* Revert the relevant parts of f5a65846a8
* Adjust the expected error message in test_exception_details_not_revealed_to_client
  since the message thrown by django-scim2 in this release is slightly
  different.

We do not have to add anything to set EXPOSE_SCIM_EXCEPTIONS, since
django-scim2 uses False as the default, which is what we want - and we
have the aforementioned test verifying that indeed information doesn't
get revealed to the SCIM client.
 		2022-02-04 15:43:45 -08:00
..
README.md docs: Fix list item indentation mistakes. 2021-08-20 23:14:37 -07:00
common.in requirements: Upgrade Python requirements. 2022-01-23 22:14:17 -08:00
dev.in requirements: Downgrade libcst. 2022-01-25 19:43:03 -08:00
dev.txt scim: Upgrade to django-scim2 0.17.1. 2022-02-04 15:43:45 -08:00
docs.in requirements: Upgrade Python requirements. 2021-09-17 17:05:18 -07:00
docs.txt requirements: Upgrade Python requirements. 2022-01-23 22:14:17 -08:00
mypy.in mypy: Add types-beautifulsoup4. 2022-01-23 23:39:40 -08:00
mypy.txt mypy: Add types-beautifulsoup4. 2022-01-23 23:39:40 -08:00
pip.in requirements: Upgrade Python requirements. 2021-05-07 22:42:39 -07:00
pip.txt requirements: Upgrade Python requirements. 2022-01-23 22:14:17 -08:00
prod.in requirements: Remove unnecessary version bounds from *.in. 2019-09-23 13:23:58 -07:00
prod.txt scim: Upgrade to django-scim2 0.17.1. 2022-02-04 15:43:45 -08:00

README.md

The dependency graph of the requirements is as follows:

dev +-> prod +-> common
+
|
v
mypy,docs,pip

Of the files, only dev, prod, and mypy have been used in the install scripts directly. The rest are implicit dependencies.

Steps to update a lock file, e.g. to update ipython from 5.3.0 to latest version:

  1. Remove entry for ipython==5.3.0 in dev.txt.
  2. Run ./tools/update-locked-requirements, which will generate new entries, pinned to the latest version.
  3. Increase PROVISION_VERSION in version.py.
  4. Run ./tools/provision to install the new deps and test them.
  5. Commit your changes.