• JASN_DE@feddit.org
    link
    fedilink
    English
    arrow-up
    19
    arrow-down
    5
    ·
    13 hours ago

    Which isn’t a great idea with all the breaking changes. I’d assume it gets better after v2, but still.

    • GraveyardOrbit@lemmy.zip
      link
      fedilink
      English
      arrow-up
      13
      ·
      6 hours ago

      Your comment is spreading false information. With the stable release the Immich team has committed to no breaking changes except for major version upgrades, so if you pin to 2.x.x you will be perfectly fine

      • skilltheamps@feddit.org
        link
        fedilink
        English
        arrow-up
        2
        ·
        5 hours ago

        That’s what I thought, but last time I looked I only saw a “release” tag, no “v2” tag. Did I miss something?

    • LastYearsIrritant@sopuli.xyz
      link
      fedilink
      English
      arrow-up
      15
      ·
      11 hours ago

      I automate my upgrades, but I also automate my backups, and monitoring.

      If an upgrade breaks something, my health monitor lets me know and I can roll back to the previous day.

    • saddlebag@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      15
      ·
      12 hours ago

      I’ve been doing this in my kubernetes cluster since immich was less than v1.49.0 (that’s the earliest I can find but it’s been over 4 years).

      Your comment could have been more constructive: something like “this is really cool, just be sure you don’t auto merge PRs without reading the patch notes. Learn about the process before you roll this out to your mission critical systems!”

      This is a learning opportunity (possibly even for you). Show others how to do things well and the whole community can benefit.