2019-04-21 05:51:20 +02:00
|
|
|
import os
|
|
|
|
|
2019-11-23 00:30:24 +01:00
|
|
|
ZULIP_VERSION = "2.1.0-rc1"
|
2019-04-21 05:51:20 +02:00
|
|
|
# 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')
|
|
|
|
if os.path.exists(zulip_git_version_file):
|
|
|
|
with open(zulip_git_version_file) as f:
|
|
|
|
version = f.read().strip()
|
|
|
|
if version:
|
|
|
|
ZULIP_VERSION = version
|
|
|
|
|
2019-03-01 02:37:46 +01:00
|
|
|
LATEST_MAJOR_VERSION = "2.0"
|
2019-11-21 21:52:00 +01:00
|
|
|
LATEST_RELEASE_VERSION = "2.0.7"
|
2019-03-01 02:37:46 +01:00
|
|
|
LATEST_RELEASE_ANNOUNCEMENT = "https://blog.zulip.org/2019/03/01/zulip-2-0-released/"
|
2017-11-16 21:40:36 +01:00
|
|
|
|
2017-12-26 07:57:39 +01:00
|
|
|
# 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.
|
|
|
|
|
2019-07-22 04:00:19 +02:00
|
|
|
# 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.
|
2017-12-26 07:57:39 +01:00
|
|
|
|
auth: Use zxcvbn to ensure password strength on server side.
For a long time, we've been only doing the zxcvbn password strength
checks on the browser, which is helpful, but means users could through
hackery (or a bug in the frontend validation code) manage to set a
too-weak password. We fix this by running our password strength
validation on the backend as well, using python-zxcvbn.
In theory, a bug in python-zxcvbn could result in it producing a
different opinion than the frontend version; if so, it'd be a pretty
bad bug in the library, and hopefully we'd hear about it from users,
report upstream, and get it fixed that way. Alternatively, we can
switch to shelling out to node like we do for KaTeX.
Fixes #6880.
2019-11-18 08:11:03 +01:00
|
|
|
PROVISION_VERSION = '66.1'
|