v1.8.0

Added

• Traefik's timeouts on the HTTPS entry point can be set from .env.
  TRAEFIK_READ_TIMEOUT, TRAEFIK_WRITE_TIMEOUT and TRAEFIK_IDLE_TIMEOUT
  default to Traefik's own values (60s, 0s, 180s), so nothing changes unless
  you set them. Traefik reads its static configuration from one source, here
  the command in the compose file, and an override file can only replace that
  command whole; a variable is the way to tune it and keep taking updates.
  The same change was asked for in the Keycloak template, and every template in the fleet gets it at once.

v1.7.7

Fixed

• A restore left behind whatever was created after the backup. It used
  mongorestore --drop, which replaces only the collections the archive
  holds, so a collection added since the backup survived the restore; the
  test knew and worked around it instead of catching it. The script now drops
  the database before loading the archive, takes the backup directory and
  name from the running backups container, accepts the file name as an
  argument, starts Rocket.Chat again whatever happens, and CI runs it: a
  document added after the backup and a collection created after it must both
  be gone once it is restored.

Changed

• The freshness check has its own workflow, Pin Freshness. It ran inside Deployment Verification, whose badge is the one at the top of this README. Across the fleet, nine red runs in ten were a pin one version behind - which the fleet's triage moves within the day - and a reader cannot tell that from a stack that does not boot. The badge now says whether the stack boots. The job itself is unchanged.

v1.7.6

Security

• traefik:3.7 was rebuilt upstream; the pin moved from sha256:1c32e7c36820… to sha256:24841fe2de73…. Same version, same tag, a rebuilt base image — the usual shape of a security fix in a base layer.

Upgrading

git pull (or ./update.sh), then docker compose up -d. Containers on a refreshed image are recreated; data volumes and .env are untouched. This release was cut by fleet triage after the deploy job booted the stack on the refreshed images.

Full history in CHANGELOG.md.

v1.7.5

Security

• traefik:3.7 was rebuilt upstream; the pin moved from sha256:f86a2cab1b5c… to sha256:1c32e7c36820…. Same version, same tag, a rebuilt base image — the usual shape of a security fix in a base layer.

Upgrading

git pull (or ./update.sh), then docker compose up -d. Containers on a refreshed image are recreated; data volumes and .env are untouched. This release was cut by fleet triage after the deploy job booted the stack on the refreshed images.

Full history in CHANGELOG.md.

v1.7.4

Security

• mongo:7.0 was rebuilt upstream; the pin moved from sha256:b096b4cb9269… to sha256:9854f7139445…. Same version, same tag, a rebuilt base image — the usual shape of a security fix in a base layer.

Upgrading

git pull (or ./update.sh), then docker compose up -d. Containers on a refreshed image are recreated; data volumes and .env are untouched. This release was cut by fleet triage after the deploy job booted the stack on the refreshed images.

Full history in CHANGELOG.md.

v1.7.3

Security

• mongo:7.0 was rebuilt upstream; the pin moved from sha256:8102f674c3d5… to sha256:b096b4cb9269…. Same version, same tag, a rebuilt base image — the usual shape of a security fix in a base layer.

Upgrading

git pull (or ./update.sh), then docker compose up -d. Containers on a refreshed image are recreated; data volumes and .env are untouched. This release was cut by fleet triage after the deploy job booted the stack on the refreshed images.

Full history in CHANGELOG.md.

v1.7.2

Changed

• rocketchat/rocket.chat:8.8.0 moved to rocketchat/rocket.chat:8.8.1. The freshness check reported the lag; the deploy job booted the stack on the new image before this landed.

Upgrading

git pull (or ./update.sh), then docker compose up -d. Containers on a refreshed image are recreated; data volumes and .env are untouched. This release was cut by fleet triage after the deploy job booted the stack on the refreshed images.

Full history in CHANGELOG.md.

What upstream changed

Read by fleet triage from the upstream release notes (or the commits between the tags) against this compose file, before the bump was applied.

Upstream changes 8.8.0 -> 8.8.1

Verdict: SAFE TO APPLY — this is a patch release with a bug fix and dependency bumps only, no breaking changes noted.

Breaking changes

• none found in the notes

Variables

• none

Data and dependencies

• Engine versions listed (Node 22.22.3, Deno 2.3.1, MongoDB 8.0, Apps-Engine 1.66.0) — note the release lists MongoDB 8.0 as the tested engine version, while the compose file pins mongo:7.0 via ROCKETCHAT_MONGODB_IMAGE_VERSION. This mismatch is worth flagging but the notes themselves state no required MongoDB upgrade or migration for this patch.
• The only functional change: "Fixes Omnichannel rooms failing to register agent responses (and showing send errors on messages and file uploads that were actually delivered) when the room carried corrupted visitor activity data created by older app integrations" — a bugfix, not a schema or config change.
• No irreversible migrations, no removed defaults, no changed ports or paths mentioned.

Before applying

• Update the pin: change ROCKETCHAT_IMAGE_VERSION default (or override) from 8.8.0 to 8.8.1 and update the digest in the compose file's x-images block (&rocketchat-image line), since this repo pins by tag+sha256.
• Take the routine precaution of a MongoDB backup before any Rocket.Chat version bump (standard practice here, not something the notes require specifically for 8.8.1).
• If running Omnichannel with older app integrations, watch for changed agent-response behavior on rooms with previously corrupted visitor activity data after upgrade — this is the fix, not a regression, but validate that affected rooms now work as expected.

Notes read

• 8.8.1 (2026-09-09) — full changelog body provided above.

v1.7.1

Security

• mongo:7.0 was rebuilt upstream; the pin moved from sha256:b6421fd6d1c5… to sha256:8102f674c3d5…. Same version, same tag, a rebuilt base image — the usual shape of a security fix in a base layer.

Upgrading

git pull (or ./update.sh), then docker compose up -d. Containers on a refreshed image are recreated; data volumes and .env are untouched. This release was cut by fleet triage after the deploy job booted the stack on the refreshed images.

Full history in CHANGELOG.md.

v1.7.0

Added

• update.sh: move between release tags on purpose. It updates to the latest release (a combination this repository's CI has booted and smoke-tested), refuses to cross a major version unattended, refuses to run over local changes, and names any new required variable before anything has moved. --dry-run says what would happen.

Upgrading

git pull (or ./update.sh). Nothing running changes: this release adds or extends the update script and touches no image pin.

Full history in CHANGELOG.md.

v1.6.0

Fixed

• A backup interrupted halfway no longer looks like a good one. The loop
  already renamed a failed dump to .failed so nothing would restore from it,
  but that rename only runs if the shell lives long enough to reach it. Stop
  the container mid-dump and it does not: the truncated file keeps the name a
  finished backup would have, and it is the newest one, which is exactly what
  the restore script and the end-to-end test pick. Every backup is now written
  to <name>.partial and renamed only after the dump succeeds, so the real
  name never exists unless the file behind it is complete. Verified by killing
  a dump in flight: before, the restore path selected a file that failed
  gzip -t; after, it finds nothing to select.