- #Hipchat download v2.2.1388 upgrade
- #Hipchat download v2.2.1388 license
- #Hipchat download v2.2.1388 free
#Hipchat download v2.2.1388 upgrade
This does not impede the upgrade functionality. The ' hipchat upgrade' command displays ' InsecurePlatformWarning'.The unread state known issues from v2.2.7 (below) still apply.You will need to reboot to apply this upgrade.We've updated several third-party libraries for security purposes. We've updated the internal authentication system. We've improved performance and stability of the internal authentication system in case of big directories synchronization. We’ve updated the Linux kernel on the appliance to use the Ubuntu LTS enablement stack.
#Hipchat download v2.2.1388 license
When you add new users, they'll only count towards the license once they log in to Hipchat.
#Hipchat download v2.2.1388 free
You can manually disable or remove some of these synchronized users if you need to free up seats on your license.
If you're upgrading to 2.4.3, we'll count all existing synchronized users towards your license count, so that everyone who used the service before can continue to use it without any changes to who they see in the "new chat" or lists. This lead to some difficulties with directory filtering rules, and a long list of possible users when starting a new chat or someone. Previously, all users synchronized from your authentication system into our internal directory were counted towards your license count. In version 2.4.3, we've changed how we count the number of people using your Hipchat instance towards your license. If you're looking for Hipchat Server v 2.3.0 or 2.3.1, those were beta releases of Hipchat Data Center and are no longer available, but you can read their historical release notes below.
The most recent stable release of Hipchat Server is below. Looking for Hipchat Server 2.3 or Hipchat Data Center beta?
See the related Hipchat Knowledge Base article for more information. If your upgrade fails with a " Mismatch of expected sha512sum" error, your upgrade binary may be out of date, corrupted, or might have only been partially downloaded.You will need to schedule the appropriate downtime for production deployments.ĭuring this upgrade, you might see some No such file or directory warning messages in the console log. To complete this upgrade, you must reboot your server to apply the changes. (You can read more in general about Ubuntu security releases here.) Versions 2.2.8 and later include changes in the underlying Ubuntu binaries which address the Meltdown and Spectre vulnerabilities.