github-releases-bot
codeberg.org
This repository contains code to scan for new releases of configurable github repositories and publish new releases to different Mastodon accounts.

I’m selfhosting several services, mostly based on docker containers. Many of these are managed on Github and publish releases there. What annoys me is that I regularly miss updates.

I’m also quite active on Mastodon so I thought it would be handy to have a bot automatically scanning for new github releases and posting a new toot for every new release.

The bot can be configured to scan multiple different github repositories and publish to different mastodon accounts.

I have set up accounts for:

https://mastodon.social/@navidrome_releases https://mastodon.social/@vaultwarden_releases https://mastodon.social/@dockerpihole_releases https://mastodon.social/@tempo_releases https://mastodon.social/@unifidocker_releases

Here’s the code, if someone is interested in that:

https://codeberg.org/ryan_harg/github-releases-bot

Is this something that people find useful? Which other services would you like to see covered in that way?

  • gla3dr@lemmy.ca
    English
    0·
    5 months ago

    Why not just subscribe to the release notifications or use the releases atom feed?

    • Eskuero@lemmy.fromshado.wsEnglish
      0·
      5 months ago

      I do it that way. Enable email notifications for new tagged releases, something arrives, check changelog, everything fine?

      docker-compose pull; docker-compose down; docker-compose up -d

      And we are done

      • Link@rentadrunk.orgEnglish
        0·
        5 months ago

        You don’t need to run docker-compose down.

        docker-compose pull; docker-compose up -d is enough

        • Eskuero@lemmy.fromshado.wsEnglish
          0·
          5 months ago

          I guess that’s fair for single service composes but I don’t really trust composes with multiple services to gracefully handle only recreating one of the containers

          • Link@rentadrunk.orgEnglish
            0·
            5 months ago

            If only one container has been updated then when you run docker compose up -d it will only recreate that container, unless it is a dependency of another container (like a database) in which case it will restart all containers that depend on it as well.

    • Ryan@discuss.tchncs.deOPEnglish
      0·
      5 months ago

      I’m just a lot more likely to notice a post on social media. I don’t use a RSS reader or pay attention to github notifications. (The bot actually reads the atom feed of a repositories releases…). But sure, if that’s something you’re using anyway, it might be perfect for you.

    • Ryan@discuss.tchncs.deOPEnglish
      0·
      5 months ago

      The bot consumes the atom feed of a repository, but I don’t use a feed reader. you could also just let Github notify you for new releases. But I don’t pay much attention to github notifications either. I’m a lot more likely to notice something like that if it’s integrated into my social media consumption.

      • gla3dr@lemmy.ca
        English
        0·
        5 months ago

        I wasn’t trying to throw shade here. I was just genuinely curious about OPs motivations for doing this. It’s totally reasonable that they could have a use case where this solution makes the most sense.

    • wall_inhabiter@lemdro.idEnglish
      0·
      5 months ago

      I get most of my RSS feeds thru Misskey.io so having downstream activitypub bridges like this, or the bluesky bridge (that ppl are freaking out about for no reason) are still really useful to me

  • rambos@lemm.eeEnglish
    0·
    5 months ago

    Is there any way to get those notifictions over selfhosted gotify?

  • synae[he/him]@lemmy.sdf.orgEnglish
    0·
    5 months ago

    You could get notified with a PR to update a version with renovate.

    (Assuming you have your selfhosting configurations checked into source control, which I realize as I’m typing this that it might not be the norm…)