Release v0.13.0 Release · LemmyNet/lemmy
github.com
Releases.md

Since our last release earlier this month, we’ve had ~30 commits to Lemmy.

Major Changes

  • Added comment and post reporting in the front end, and cleaned up the reporting API.
    • Note: these are local-only currently, reports are not yet federated.
  • The JWT secret is now auto-generated by the database.
    • Note: this will log out all users, so users will have to log in again.
  • Lots of smaller UI fixes listed below.

Upgrade notes

Servers

If you’d like to make a DB backup before upgrading, follow this guide.

To upgrade your instance to v0.13.0, simply follow the instructions in the documentation:

Changes

Lemmy Server

General

  • Adding a user agent. Fixes #1769
  • Ansible changes (#1781)
  • Clean up reporting (#1776)
  • Implement webmention support (fixes #1395)
  • Move jwt secret from config to database (fixes #1728)
  • Set a 10 char minimum password length.
  • Dont pass accept-encoding header to pictrs (ref #1734) (#1738)

API

  • There are no breaking API changes, only the addition of reporting endpoints.
  • A full list of the API changes can be seen on this diff of lemmy-js-client: 0.12.0 -> 0.13.0 .

Federation

  • Rewrite fetcher (#1792)

Lemmy UI

  • Adding bn, ml, and cs langs
  • Reporting (#434)
  • Splitting login and signup pages. Fixes #386 (#431)
  • Fixing image in newtab. Fixes #382 (#430)
  • Navigate away from login page if already logged in. (#429)
  • Add username validation message. Fixes #387 (#428)
  • Password strength meter (#427)
  • Fix community display name overflow. Fixes #390 (#425)
  • Fix logout bug. Fixes #391 (#424)
  • Fix up post, profile and community forms. Fixes #409 (#423)
  • Adding markdown audio and video embeds. Fixes #420 (#421)
  • Adding Si simplifier (#418)
  • Fix profile paging. Fixes #416 (#417)
  • Use my fork of inferno-i18next. Fixes #413 (#415)
  • Add version to package.json . Fixes #411
  • Tmpod
    3•3 years ago

    Does this mean the JWT config option is deprecated then?

    • @nutomicMA
      4•3 years ago

      Yes you can just remove it from the config after upgrading.

  • @je_vv
    3•2 years ago

    deleted by creator

    • DessalinesOPMA
      4•3 years ago

      2 ways to change it:

      • Use a browser that supports dark mode, and make sure your theme in your user settings is Browser Default (which it should be by default.
      • Manually change your theme in settings to darkly.
      • @je_vv
        2•2 years ago

        deleted by creator

        • DessalinesOPMA
          2•3 years ago

          The prefers color scheme that browsers have now, only has light and dark mode currently.

    • @poVoq
      3•1 year ago

      deleted by creator

      • @je_vv
        2•2 years ago

        deleted by creator

    • DessalinesOPMA
      1•3 years ago

      They can’t login? I don’t understand.

        • DessalinesOPMA
          1•3 years ago

          They need to open an issue, I don’t have enough info.

    • DessalinesOPMA
      2•3 years ago

      You re-logged in on mobile?

      I just tested on mobile and it works.

        • DessalinesOPMA
          1•3 years ago

          I’d need to see console logs, there’s no other way I could figure out the error. In your screenshot you have no post title, and that’s required (and it should tell you that).