Zulip Server 4.6 bug fix release
We released Zulip Server 4.6 today! This is a bug fix release, containing a few dozen cherry-picked changes since Zulip Server 4.5.
This release fixes the following issues:
- Documented official support for Debian 11 Bullseye, now that it is officially released by Debian upstream.
- Fixed installation on Debian 10 Buster. Upstream infrastructure had broken the
virtualenvtool on this platform, which we’ve worked around for this release.
- Zulip releases are now distributed from
replacing the old
- Added support for LDAP synchronization of the
git fetch --prune; this ensures
upgrade-zulip-from-git masterwith return an error rather than using a stale cached version of the
masterbranch, which was renamed to
- Added a new
reset_authentication_attempt_countmanagement command to allow sysadmins to manually reset authentication rate limits.
- Fixed a bug that caused the
upgrade-postgresqltool to incorrectly remove
- Fixed a rare migration bug when upgrading from Zulip versions 2.1 and older.
- Fixed a subtle bug where the left sidebar would show both old and new names for some topics that had been renamed.
- Fixed incoming email gateway support for configurations with the
- Fixed issues where the Slack-compatible interface outgoing webhook variant had a different format from Slack’s documented interface.
- The installation and upgrade documentations now show the latest release’s version number.
- Backported many improvements to the ReadTheDocs documentation.
- Updated translation data from Transifex.
We recommend that all installations upgrade to this new release. See the upgrade instructions in the Zulip documentation. If you need help, best-effort support is available in #production help in the Zulip developer community.
We love feedback from the Zulip user community. Here are a few ways you can participate:
- The Zulip developer community is the best place to provide feedback. Many feedback conversations lead to concrete changes in Zulip, its documentation, or our priorities.
- Follow us on Twitter, or join our announcement mailing list (or subscribe to the blog posts, which are mostly a subset of the already low-volume mailing list).
- Contribute financially to the project by sponsoring Zulip.