News
join-lemmy.org

What is Lemmy?

Lemmy is a self-hosted social link aggregation and discussion platform. It is completely free and open, and not controlled by any company. This means that there is no advertising, tracking, or secret algorithms. Content is organized into communities, so it is easy to subscribe to topics that you are interested in, and ignore others. Voting is used to bring the most interesting items to the top.

Major Changes

This version fixes the problem of comment context not loading properly. It also fixes a couple other bugs.

Support development

@dessalines and @nutomic are working full-time on Lemmy to integrate community contributions, fix bugs, optimize performance and much more. This work is funded exclusively through donations.

If you like using Lemmy, and want to make sure that we will always be available to work full time building it, consider donating to support its development. No one likes recurring donations, but they’ve proven to be the only way that open-source software like Lemmy can stay independent and alive.

Upgrade instructions

Follow the upgrade instructions for ansible or docker. There are no config or API changes with this release.

If you need help with the upgrade, you can ask in our support forum or on the Matrix Chat.

  • A10@kerala.party@kerala.partyEnglish
    6·
    1 year ago

    thanks for the arm builds, I am currently using masquernya/lemmy-arm64.git for arm builds. How do you handle the lemmy-translations update in your build pipeline for lemmy-ui?

    I do not see you doing the following, or did I miss something

    # manual updates
cd lemmy-translations/;
git checkout "$TRANSLATION_COMMIT" || exit 1;

    also do you have to trigger the build manually when a new lemmy version is out ?

    • Jonny@lemmy.rimkus.itEnglish
      41·
      1 year ago

      Hi, Thanks for the hints, and yes I have to trigger the pipeline by editing and commiting the Version information here

      do I really need

      cd lemmy-translations/;
git checkout "$TRANSLATION_COMMIT" || exit 1;

      even if I have

      git submodule init
git submodule update

      See here and here

      • nutomic@lemmy.mlMEnglish
        3·
        1 year ago

        You can run git submodule update, then it will pull the same translations as specified in the lemmy repo. Or run git submodule update --remote, then it will pull the latest commit from lemmy-translations.

        • Jonny@lemmy.rimkus.itEnglish
          3·
          1 year ago

          Thanks, so my pipeline should be fine in the sense that it uses the commit of the submodule, stored in the version tagged lemmy commit

      • A10@kerala.party@kerala.partyEnglish
        11·
        1 year ago

        I just tested it, submodule init+update pulls the latest commit of submodules, this could be different from the commit used in the tagged release version