Profanity 0.17.0
jubalhJust 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:
- Conventional Commit Structure: We adopted Conventional Commits (such as
feat(omemo): ...orfix(ui): ...). This standardizes our git history and allows scripts to automatically categorize changes for release notes. Our CI verifies commit formatting usingcommitlint. - Developer Certificate of Origin (DCO): We now require commits to be signed off using
git commit -s, which appends aSigned-off-by: Name <email>line. This is standard OSS practice to confirm that contributions are submitted under the project’s license (GPL-3.0-or-later). Our CI verifies this via a DCO check. - Code Formatting: The CI runs
clang-formatto ensure consistent style. - Spell Checking: We run
codespellin CI across all code, comments, and documentation to catch typos before they land. - Automated Testing: Dedicated CI jobs run our unit tests (via
cmocka), functional tests (viastabber), static analysis (-fanalyzer), sanitizers, and builds across various Linux distros and test the build on Cygwin.
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
- Added OMEMO trust status indicators directly to the titlebar.
/omemo fingerprintnow shows active and trust status.- Added user notifications when new OMEMO devices or fingerprints are discovered, while suppressing redundant “session already exists” and missing device ID warnings.
- Descriptive error messages for OMEMO decryption failures.
- Incoming spam and abuse reports (XEP-0377) are now displayed.
- Stricter JID validation across commands like
/msg,/sub, and/blocked.
UI & Miscellaneous
- Color coded status messages for file transfers.
- Added dynamic pad resizing and UTF-8 character support in tab autocompletion.
- Sanitized illegal XML characters from outgoing messages.
Details
For the full list of bug fixes, refactorings, and cleanup in this release, please head over to the 0.17.0 release notes.