⬆️ Upgrade wps-office to 11.1.0.11723-ls144

[github-actions]

WPS Office is on 11.1.0; upstream released 11.1.0.11723-ls144 on 2025-12-08 (patch bump).

Changes to apply

• hub/wps-office/stack.yaml
  • version: "11.1.0" → version: "11.1.0.11723-ls144"
• hub/wps-office/stack.yaml
  • updated_at: 2025-03-03 → updated_at: 2025-12-08
• hub/wps-office/compose.yaml
  • ${WPS_OFFICE_VERSION:-:11.1.0} → ${WPS_OFFICE_VERSION:-:11.1.0.11723-ls144}

Warning

No published container tag was found for this version. Confirm the image exists before doing anything else — a release without an image is not shippable.

Warnings

• could not list tags for linuxserver/wps-office (other)

Required before merging

A newer release is not evidence that the new version still works with our
compose file, our .env and our volumes. Establish a baseline first, then
prove the bump did not regress it:

# 1. baseline: does it pass today, before any change?
./packages/scripts/maintenance/test-stack.sh wps-office

# 2. apply the edits above, then:
./packages/scripts/maintenance/test-stack.sh wps-office

The test pulls every image, waits for all services to become healthy, checks
that nothing crash-loops during a settle window, and makes a real HTTP request
to the app's entry point.

• If the baseline fails too, this app was already broken: fix that first or say
  so in the PR — it is not a regression from this bump.
• If the baseline passes and the bump fails, do not merge. Read the release
  notes: a required new env var or a migration usually needs .env or
  compose.yaml changes alongside the version.
• Attach the test output to the PR.

_{Filed automatically from work/version-drift.json.}