Skip to content

v0.7.0

Choose a tag to compare

View all tags
@simonvanlierde simonvanlierde released this 27 Oct 13:37
v0.7.0
bd70feb
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Upgrading:

  • Upgrade the R9lab backend first. This release needs one that serves the /v1/plugins/r9cam
    routes and accepts the r9cam-relay token audience: the hosted api.r9lab.io does, a
    self-hosted R9lab v0.5.0 or older does not. Pis on 0.6 keep working with a current backend
    until 2027-01-31, so upgrade them before then.
  • Docker Compose now pulls the release image: run git pull first, then docker compose pull
    and docker compose up -d. Standalone installs: set R9CAM_IMAGE=r9cam in .env and run
    docker compose build instead of pull.
  • Paired cameras stay paired when Docker Compose is upgraded in place and on installs without
    Docker. A fresh clone into an r9cam/ directory starts with empty volumes. See "Upgrading
    From 0.6" in INSTALL.md for both cases.
  • With S3 storage, new captures go under the r9cam/ key prefix. Objects already stored stay
    under rpi-cam/; nothing moves them. Dashboards and alerts that filter
    on job="rpi-cam-plugin" or rpi_cam_* metrics must switch to job="r9cam" and r9cam_*.

Added

  • Each release publishes a signed linux/arm64 image to ghcr.io/cmlplatform/r9cam, tagged
    with the version, X.Y and latest, so the Pi pulls it instead of building it. Its build
    provenance and SBOM are attested: gh attestation verify oci://ghcr.io/cmlplatform/r9cam@<digest> --repo CMLPlatform/r9cam checks them. R9CAM_VERSION in .env pins a release; the default is latest. (#87)

Changed

  • Breaking: the plugin is now r9cam, and its shared models package is r9cam-models
    (was relab-rpi-cam-models). Renamed with it: the R9CAM_CREDENTIALS_FILE variable, the
    ~/.config/r9cam credentials directory, the _r9cam._tcp mDNS service type, the r9cam
    OpenTelemetry service.name, /healthz service, the r9cam_session cookie,
    openapi.r9cam.json and the device token audience r9cam-relay. INSTALL.md has the full
    table. (#45, #48)
  • Breaking: the last rpi-cam names follow the rename: Prometheus metrics are r9cam_*
    (was rpi_cam_*), the Alloy job label and default instance are r9cam (was
    rpi-cam-plugin), the default S3 key prefix is r9cam/ (was rpi-cam/), the example bucket
    is r9cam, and the container user is r9cam. (#86)
  • Breaking: the Pi calls only the /v1/plugins/r9cam routes and the default pairing
    backend is https://api.r9lab.io. (#79)
  • Pairing polls with POST and a JSON body, as the current backend expects. (#46)
  • EXIF capture details (exposure, offset time, temperature) are written to the Exif block, and
    Software names the r9cam version.

Fixed

  • The upload queue stays under its byte cap when captures arrive at the same time. (#61)
  • Captures that ran out of upload retries, for example while the Pi was unpaired, are queued
    again after a successful pairing. Any that no longer fit under the queue's limits stay in
    data/queue/dead/. (#85)
  • local_setup.sh installs uv from a release archive it checks against its checksum. (#68)
  • Installs without Docker keep their pairing across the rename, and RELAB_CREDENTIALS_FILE
    still works with a warning. (#79)
  • The wheel and sdist include the AGPL license text. (#90)
  • The relay keeps retrying when the backend refuses its handshake (401, 403, 404, 429 and
    the like), with the usual backoff and a warning that names the status, instead of stopping
    until the next restart. On a 401 or 403 the warning says the camera may need re-pairing. (#84)

Security

  • Dependencies locked past advisories in aiohttp, pillow, urllib3, pyjwt, multidict,
    opentelemetry and certifi. (#42, #58, #63)
  • Releases carry the wheel, the sdist and a CycloneDX SBOM (r9cam.cdx.json), each with a
    build provenance attestation.
Assets 5
Loading