How do Docker images and GitHib release versions relate for Baby Buddy?

[skjdghsdjgsdj]

My docker-compose.yml looks vaguely like this:

services:
  babybuddy:
    image: lscr.io/linuxserver/babybuddy
    container_name: babybuddy
    environment:
      - TZ=...
      - CSRF_TRUSTED_ORIGINS=...
      - ALLOWED_HOSTS=...
      - PROXY_HEADER=HTTP_X_AUTHENTIK_USERNAME
      - REVERSE_PROXY_AUTH=True
    volumes:
      - /root/babybuddy/appdata:/config
    ports:
      - 8000:8000
    restart: unless-stopped

Occasionally I run a docker compose pull && docker compose up -d and I get new versions of Baby Buddy, despite no new releases showing up in GitHub. Yes, I'm performing the sin of using an implicit :latest version tag, but is this pulling a bleeding edge build from the main branch, the latest stable release from GitHub (doesn't look like it), or something else?

Is it possible to change my Docker compose config to opt for the latest stable release from GitHub?

And fret not about the reference to /root; this is contained within a Proxmox LXC so it doesn't really have root access to the host.

[cdubz]

I assume that’s bleeding edge master branch.

I think LSIO has a community where you could ask. I’m also not sure how to do what you’re looking for. Happy to adjust the build and release flow to accommodate.

[skjdghsdjgsdj]

Thanks. I didn't know this was something maintained by someone else, so I can check over there.