maziggy 7bd85692f5 fix(slicer): name the sidecar service in the update command (#2802) ...

The "update your sidecar image" advice told users to run a bare
    `docker compose pull`. bambu-studio-api is declared with
    `profiles: [bambu]`, and compose skips profile-gated services silently,
    so the pull was a no-op for exactly the users the message was written
    for -- and `restart: unless-stopped` kept the old container serving.
    The reporter pulled, restarted, set MAX_MODEL_UPLOAD_MB and got the same
    100 MB rejection, because the image never changed.

    Name the service in both commands instead. Naming enables the profile
    implicitly, for pull and up alike. `--profile bambu` would also work but
    downloads the 220 MB Bambu image on an OrcaSlicer-only host and then
    starts a sidecar the user never asked for.

    Same correction in the sidecar README, the compose header and the
    changelog entry, which all carried the bare form.

2026-08-15 14:53:13 +02:00

..

app

fix(slicer): name the sidecar service in the update command (#2802)

2026-08-15 14:53:13 +02:00

tests

Explain Bambu Cloud's CAPTCHA challenge instead of repeating it (#2790)

2026-08-15 14:42:27 +02:00

__init__.py

…