3.7.6

Two of these are the product doing what it already said it did. One is a command-line tool that stopped mixing its errors into its answers.

Upgrading is hitechcloudcli update.

Breakout rooms you can actually open​

3.7.4 said "a host can split a meeting into rooms, move people between them, speak into all of them at once, and bring everybody back". The server could do all of that. The meeting room had no way to ask it — searching the whole client for the word turned up nothing — so no host could. That sentence is now true.

A moderator gets a Breakout rooms tab: make a room, move somebody in by picking a destination, bring one person or everybody back, and say something into every room at once. Everybody else sees the same list, read-only, because who went where is not private — but only a moderator may change it, so the panel shows what it shows instead of offering buttons the server would refuse. Somebody in a breakout is told which one, and that the main meeting cannot hear it.

The meeting settings panel stops advertising a recording destination​

It showed every moderator a block headed External Recording Stream, reading "Direct RTMP/S3 destination sync: Active", over a copyable rtmp:// address. None of it existed: there is no RTMP or S3 destination anywhere in the conferencing service — a recording is written to this server as WebM and composited with ffmpeg — live streaming goes to a URL the host types into the live-stream dialog, and the hostname in that address did not resolve. An operator could copy it, point something at it, and wait for a stream that was never going to arrive.

Third claim of that shape after the end-to-end-encryption badge and the "AI" noise suppression pill, both corrected in 3.7.4. The rule that catches them: a badge naming a capability has to be able to point at the code that does it.

The CLI says what it means​

• An error goes to stderr. 75 messages across 26 files were printed to stdout — where the answer goes. Both panels read a command's stdout at 193 places, so an error there arrives where data was expected: a list with Error: ... in it, or JSON that will not parse. 70 moved. Five deliberately did not: api, email-setup, email-webmail, email-quotas and email-sendlimit answer "Community edition does not support ..." on stdout because the panel matches that text to decide where the webmail link points. That is the command's answer, not a failure, and each of those five now says so in place.
• hitechcloudcli <command> --help answers the same way whatever the program is invoked as. Under the installed name it always did. Under any other name it was handed to the command as an argument — and a command that does not parse --help takes it for a value and runs: a domain called --help to look up, a site by that name to scan, an account whose files to chown. Nothing existed under those names, so nothing was damaged, but the command ran.
• Four commands stop advertising eleven flags nothing implements. docker-limits, docker-logs, docker-images and docker-autostart promised --apply, --read, --all, --system, --users, --dry-run, --force-update, --set, --add, --remove and --clear between them. All four ignore their arguments and print a notice, and there are no shell twins, so an operator typing exactly what --help told them to type got nothing. They also claimed to be "only available on the container stack" in the branch that runs on one, which is the single place that is certainly false.

Three checks now hold the line, and each was verified by making it fail on purpose: errors on stdout, a usage string promising a flag the code ignores, and a command with no help text to print.

Fixed​

• A dry run of an update script writes nothing, including the version file. HITECHCLOUD_UPDATE_DRY_RUN=1 used to record the new version before any other check, and an update runs every intermediate release's script in order — so a dry run of a three-release upgrade rewrote the version three times, and a real update afterwards could skip what it thought was already done. Fixed in 3.7.3, 3.7.4 and 3.7.5's scripts, all of which still run on upgrade paths.
• The documentation says the version that is released. The site's label had been three releases behind.