Profanity Illustration

Profanity

Developer Blog

Profanity 0.17.0

jubalh

Just one month and 226 commits after 0.16.0, we released Profanity 0.17.0 in March 2026.

3 people contributed code to this release: @botantony, @sjaeckel, and @jubalh.

If you would like to support Profanity development: please donate.

Build System & Meson Tarballs

The last release (0.16.0) was the first that could be compiled with the Meson build system. It provided a tarball for autotools and a separate one for meson. The autotools tarball was done so that distributions don’t need dependencies on automake, autoconf, and libtool.

Several distributions are dropping vendor tarballs and use git checkouts or autogenerated tarballs nowadays. Meaning they need to run the above mentioned tools in the case of the autotools build anyways.

So this release will only be shipped with tarballs generated with meson. Profanity can still be compiled with both autotools or meson for easier adjustments. Autotools users just need to generate configure first. The next release will only use Meson. So we encourage everybody to build with Meson already and report any bugs they encounter.

Enabling Functional Tests

Another big goal for 0.17.0 was to have our functional tests enabled again. They had been disabled for many years, leaving only our unit tests active in testing.

We finally reenabled functional tests again! It would be appreciated if we could find people who want to help us expand the unit and functional tests so we are less likely to introduce regressions when we rewrite existing code.

Contribution Guidelines & Automated Checks

To keep our codebase clean, consistent, and maintainable, we formalized our contribution rules and introduced automated CI checks for pull requests:

You can run these checks locally before pushing using our new quality-check.sh script or via git pre-commit hooks. For all details and examples, check out our refreshed CONTRIBUTING.md

Continuous Integration Overhaul

Along with the test revamp, we made huge improvements to our CI workflow. The CI now clearly displays exactly what is being tested across dedicated jobs: unit tests, functional tests, spell checking, and coding guidelines. We also added a unified qualitycheck script and git hook support to make running these checks locally straightforward.

Changelog Helper Script

To make release management easier, we introduced a new helper script (changelog-helper.py) that helps us create and format the CHANGELOG file much easier. This ensures consistent categorisation and saves substantial time during releases. And this is also the reason why we enforce certain guidlines now so this script can work well. You can read more about it in CONTRIBUTING.md.

Support for libomemo-c

This release introduces support for libomemo-c as an OMEMO backend.

OMEMO & Security Polish

UI & Miscellaneous

Details

For the full list of bug fixes, refactorings, and cleanup in this release, please head over to the 0.17.0 release notes.