• FackCurs@lemmy.world
    link
    fedilink
    English
    arrow-up
    7
    ·
    edit-2
    2 hours ago

    Is it standard practice to release the security updates on GitHub?

    I am a very amateur self hoster and wouldn’t go on the github of projects on my own unless I wanted to read the “read me” for install instructions. I am realizing that I got aware I needed to update my Jellyfin container ASAP only thanks to this post. I would have never checked the GitHub.

    • irmadlad@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      19 minutes ago

      I am realizing that I got aware

      I don’t run the arr stack, but this is key. You really should do your due diligence before you update anything. Personally, I wait unless it’s a security issue, and use all the early adopters as beta testers.

    • ShortN0te@lemmy.ml
      link
      fedilink
      English
      arrow-up
      3
      ·
      51 minutes ago

      Is it standard practice to release the security updates on GitHub?

      Yes.

      And then the maintainers of the package on the package repository you use will release the patch there. Completely standard operation.

      I recommend younto read up on package repositories on Linux and package maintainers etc.

    • SayCyberOnceMore@feddit.uk
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 hours ago

      Not really.

      Depending on how you install things, the package maintainers usually deal with this, so your next apt update / pacman -Syuv or … whatever Fedora does… would capture it.

      If you’ve installed this as a container… dunno… whatever the container update process is (I don’t use them)

      • FackCurs@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        43 minutes ago

        I indeed use a container. Wasn’t familiar with the update process for containers but now know how to do it.