mirror of
https://github.com/zulip/zulip.git
synced 2025-10-23 04:52:12 +00:00
a1fa2a8cf5
The new release adds the commit:20ac22b96dWhich 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 off5a65846a8* 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.
52 lines
2.0 KiB
Python
52 lines
2.0 KiB
Python
import os
|
|
|
|
ZULIP_VERSION = "5.0-dev+git"
|
|
|
|
# Add information on number of commits and commit hash to version, if available
|
|
zulip_git_version_file = os.path.join(
|
|
os.path.dirname(os.path.abspath(__file__)), "zulip-git-version"
|
|
)
|
|
lines = [ZULIP_VERSION, ""]
|
|
if os.path.exists(zulip_git_version_file):
|
|
with open(zulip_git_version_file) as f:
|
|
lines = f.readlines() + ["", ""]
|
|
ZULIP_VERSION = lines.pop(0).strip()
|
|
ZULIP_MERGE_BASE = lines.pop(0).strip()
|
|
|
|
LATEST_MAJOR_VERSION = "4.0"
|
|
LATEST_RELEASE_VERSION = "4.9"
|
|
LATEST_RELEASE_ANNOUNCEMENT = "https://blog.zulip.com/2021/05/13/zulip-4-0-released/"
|
|
|
|
# Versions of the desktop app below DESKTOP_MINIMUM_VERSION will be
|
|
# prevented from connecting to the Zulip server. Versions above
|
|
# DESKTOP_MINIMUM_VERSION but below DESKTOP_WARNING_VERSION will have
|
|
# a banner at the top of the page asking the user to upgrade.
|
|
DESKTOP_MINIMUM_VERSION = "5.2.0"
|
|
DESKTOP_WARNING_VERSION = "5.4.3"
|
|
|
|
# Bump the API_FEATURE_LEVEL whenever an API change is made
|
|
# that clients might want to condition on. If we forget at
|
|
# the time we make the change, then bump it later as soon
|
|
# as we notice; clients using API_FEATURE_LEVEL will just not
|
|
# use the new feature/API until the bump.
|
|
#
|
|
# Changes should be accompanied by documentation explaining what the
|
|
# new level means in templates/zerver/api/changelog.md, as well as
|
|
# "**Changes**" entries in the endpoint's documentation in `zulip.yaml`.
|
|
API_FEATURE_LEVEL = 115
|
|
|
|
# Bump the minor PROVISION_VERSION to indicate that folks should provision
|
|
# only when going from an old version of the code to a newer version. Bump
|
|
# the major version to indicate that folks should provision in both
|
|
# directions.
|
|
|
|
# Typically,
|
|
# * adding a dependency only requires a minor version bump;
|
|
# * removing a dependency requires a major version bump;
|
|
# * upgrading a dependency requires a major version bump, unless the
|
|
# upgraded dependency is backwards compatible with all of our
|
|
# historical commits sharing the same major version, in which case a
|
|
# minor version bump suffices.
|
|
|
|
PROVISION_VERSION = "174.0"
|