mautrix-signal: 0.8.1 -> 0.8.2

[SchweGELBin]

https://github.com/mautrix/signal/releases/tag/v0.8.2

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[Ma27]

Keep in mind that libsignal-ffi also needs an update and it needs to match exactly what mautrix-signal is using. Otherwise we're subject to unexpected bugs.

I did it myself this time since I only noticed after deploying this to my own setup for testing 🙈

[nixpkgs-ci]

Successfully created backport PR for release-24.11:

• [Backport release-24.11] mautrix-signal: 0.8.1 -> 0.8.2 #400325

[nixpkgs-ci]

Git push to origin failed for release-24.11 with exitcode 1

[SchweGELBin]

Keep in mind that libsignal-ffi also needs an update and it needs to match exactly what mautrix-signal is using. Otherwise we're subject to unexpected bugs.

I did it myself this time since I only noticed after deploying this to my own setup for testing 🙈

Alright thanks. I didn't know this.