Skip to content

Releases: quotient-im/libQuotient

Version 0.6.10

03 Oct 03:33
Compare
Choose a tag to compare

Yet another maintenance release of the stable branch, fixing an issue (#510) with invites not showing up in some cases (especially on less active/smaller accounts) - thanks to @TobiasFella for spotting that.

Version 0.6.9

12 Sep 04:29
Compare
Choose a tag to compare

Here's one more stable branch release of libQuotient, fixing a rare assertion failure due to uninitialised read marker when new events arrive and all history is already loaded. Thanks to @ptman for his help with pinning this down.

Version 0.6.8

24 Aug 05:52
Compare
Choose a tag to compare

More fixes in the stable branch led to a release of another maintenance version. The biggest change is described in detail in #464 (developers, please make sure to read it): after many months of conflating the two, libQuotient now distinguishes between read receipts and fully read markers. Unfortunately, this could not be completely done with the current 0.6.x API but the new behaviour in the stable branch strives to improve the situation without breaking (most of) existing conventions. Some conventions were broken though; if that affects you, contact the author of these words. Meanwhile, the new API for read receipts and fully read markers will soon be merged into the master branch.

Other changes include:

  • (#481) Retain the current room member avatar when renaming the user for the room.
  • (#489) When displaying the room, notification/highlight counters are no more reset. This never really worked, with the notification and highlight counts jumping to zero and then back to the original value if the timeline hasn't been completely read; now that read receipts are correctly sent, the counters can be left to the homeserver to update (while E2EE is not around).
  • (8398e71) Fix the missing percent encoding in User::fetchProfile(), leading to problems around historical userids that still have slashes.
  • (607d860, ebea54b) CS API files have been regenerated from the new matrix-doc after revamping the layout and tooling; the library API didn't change, but doc-comments are now in Markdown rather than ReStructured Text.
  • (1e70bbb) Update GTAD configuration to version 0.8 of the tool.
  • (a83ec90) Fix potential linking errors around quotient_common.h.

Version 0.6.7

07 Jun 12:40
Compare
Choose a tag to compare

One more maintenance release at the stable branch, fixing #471 that affects NeoChat - thanks to @CarlSchwan for pinpointing and suggesting a fix to it.

Version 0.6.6

17 Mar 20:25
Compare
Choose a tag to compare

Another update on the stable branch, to address #456 (possible crash on some malformed user ids).

Version 0.6.5

21 Feb 21:29
Compare
Choose a tag to compare

Yet another update on the stable branch, while 0.7 is in the works. Changes:

  • (#448, #449) Fix rich replies handling - thanks to @rpallai
  • (#453) Support abbreviated aka Reddit-style type specifiers in Matrix URIs (e.g., matrix:r/quotient:matrix.org)

Version 0.6.4

15 Jan 16:00
Compare
Choose a tag to compare

The next version on the stable branch. Highlights:

  • (#427, #437) Several fixes around homeserver resolution (thanks to the Neochat team for reporting and help with testing).
  • (#431) The project now uses GitHub Actions instead of Travis CI for Linux/macOS CI.

Version 0.6.3

24 Dec 18:49
Compare
Choose a tag to compare

Merry Christmas (to those who celebrate it)! Here comes another bugfix release of the libQuotient stable branch, including:

  • (#412 with an additional fix in e7c9ca9) Take profile data from the previous user state for users who already left
  • (693241d) Fix defunct network requests stalling the request queue
  • (e81117f, 6e8be18) Minor performance improvements on loading rooms and accounts involving many users (0.7 will have more work on handling that)
  • (2340f3d) Power level events are properly redacted now locally
  • (ff2cb9f) Work around lack of native Qt support for request bodies in DELETE requests - thanks to @TobiasFella for finding and fixing
  • (97b0bec) Fix a few cases of insufficient escaping in Quotient::Uri (thanks to nephele for reporting)
  • (#421) Fix incorrect processing when a network request (especially for .well-known) returns 404 with non-empty body that is not JSON (which is quite usual when a .well-known record is missing)
  • (66972c8) Room tags that start with . (fullstop) are no more considered correct and will get u. in front of them.

Many thanks for all the help in testing and contributing!

Version 0.6.2

23 Oct 16:20
Compare
Choose a tag to compare

A bugfix release of libQuotient that will be used for the next Quaternion beta (and, if it's good enough, the release):

  • (3c85f04) More stringent serverpart checks in user ids.
  • (948be2e) Uri::toUrl() now returns an actually working matrix.to link.

Version 0.6.1

04 Sep 20:20
Compare
Choose a tag to compare

The work on the upcoming Quaternion 0.0.9.5 led to a few fixes and optimisations in libQuotient 0.6 - this release rolls them up:

  • (5849686, 812e460) The biggest change in this release is a rewrite of the code maintaining user profiles (generic and per-room). The new code is simpler, faster and occupies less memory - a hat-trick of optimisation. The improvement is most noticeable when opening bigger rooms with many users (such as Matrix HQ).
  • (c306470, cb47079) Trying to set displayname or avatar URL to an empty value with Synapse homeservers led to an obscure error; now it works as it should.
  • (eedfd50, d886638) Another noticeable change is that the library should be more robust against gateway/CDN/proxy errors that sometimes bring unexpected responses (e.g. an HTML payload when JSON is expected).
  • (6d40d7b) Quotest: added a test for changing the user display name
  • (776c2fd) User::bridged() and User::rawName() has long been useless, as Matrix stopped using bridge postfixes - they are deprecated now.
  • (bc105c2) When compiled with Qt 5.15, the library ignores (no more functional) bearer management instead of working around its shortcomings.
  • Smaller optimisations, cleanup and documentation updates, as usual.