Update changelog and versions following Zulip Server 1.7.2.

This commit is contained in:
Tim Abbott 2018-04-10 13:43:43 -07:00
parent d4b88e86cc
commit fea65cbb01
3 changed files with 18 additions and 2 deletions

View File

@ -54,7 +54,7 @@ author = 'The Zulip Team'
# The short X.Y version. # The short X.Y version.
version = '1.7+git' version = '1.7+git'
# The full version, including alpha/beta/rc tags. # The full version, including alpha/beta/rc tags.
release = '1.7.1+git' release = '1.7.2+git'
# This allows us to insert a warning that appears only on an unreleased # This allows us to insert a warning that appears only on an unreleased
# version, e.g. to say that something is likely to have changed. # version, e.g. to say that something is likely to have changed.

View File

@ -166,6 +166,22 @@ discoverable.
- Backend test coverage is now 95%. - Backend test coverage is now 95%.
- Countless other little bug fixes both in the backend and the UI. - Countless other little bug fixes both in the backend and the UI.
### 1.7.2 -- 2018-04-12
This is a security release, with a handful of cherry-picked changes
since 1.7.1. All Zulip server admins are encouraged to upgrade
promptly.
- CVE-2018-9986: Fix XSS issues with frontend markdown processor.
- CVE-2018-9987: Fix XSS issue with muting notifications.
- CVE-2018-9990: Fix XSS issue with stream names in topic typeahead.
- CVE-2018-9999: Fix XSS issue with user uploads. The fix for this
adds a Content-Security-Policy for the `LOCAL_UPLOADS_DIR` storage
backend for user-uploaded files.
Thanks to Suhas Sunil Gaikwad for reporting CVE-2018-9987 and w2w for
reporting CVE-2018-9986 and CVE-2018-9990.
### 1.7.1 -- 2017-11-21 ### 1.7.1 -- 2017-11-21
This is a security release, with a handful of cherry-picked changes This is a security release, with a handful of cherry-picked changes

View File

@ -1,4 +1,4 @@
ZULIP_VERSION = "1.7.1+git" ZULIP_VERSION = "1.7.2+git"
# Bump the minor PROVISION_VERSION to indicate that folks should provision # 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 # only when going from an old version of the code to a newer version. Bump