Release/1.1.5

See merge request pleroma/pleroma!1954

This release brings a major performance imrovement, see
https://github.com/martinsvalin/html_entities/pull/17

Probably fixes the issue hj had, where polls would have different
counters between endpoints.

Release/1.1.4 - user.info fix plus NOT NULL for user.info

See merge request pleroma/pleroma!1927

kaniini authored Nov 03, 2019 and lain committed Nov 04, 2019

We call Object.normalize/1 to get the child object for situations like Announce.
However, the check is flawed and immediately fails if Object.normalize/1 fails.
Instead, we should use the activity itself in those cases to allow activities which
never have a child object to pass through the filter.

Closes #1291

This sets info->muted_notifications to an emtpy array if it is explicitly set
to null before. This can happen when safe_jsonb_set coalesces to a jsonb null,
which will make ecto not use the default value of [] anymore because it has been
explicitly overwritten.

rinpatch authored Oct 30, 2019 and lain committed Nov 01, 2019

This resulted in failures when updating from Pleroma <1.0 because of all
the new fields that were added to the user schema.

1.1.3 release

See merge request pleroma/pleroma!1884

This is not what with_muted is for per documentation and it was agreed
on irc that this behavior doesn't make sense.

1.1.2 Release

See merge request pleroma/pleroma!1863

1.1.1 Release

See merge request pleroma/pleroma!1857

While the case tested (`lain@ple`) gives wrong ordering due to
using only trigram to order, it almost never happens in reality. In reality
it would be either `lain` (in which case it's fine to list the user with `lain`
in display name first), or `@lain@pleroma.soykaf.com`/`lain@pleroma.soykaf.com` (which is
handled fine as well)

- Remove trigram as it tends to rank garbage results highly, resulting
in it prioritized above fts, which gives actually decent results. ACKed
by kaniini and lain on irc.
- Remove a test for handling misspelled requests, since we no longer have
trigram
- Remove a test for searching users with `nil` display names, because it
is unrealistic, we don't accept usernames that are not >1 char strings
- Make rank boosting for followers/followees sane again, previous values
resulted in garbage matches getting on top just because the users are
followers/followees

Fix a migration wiping user info of users that don't have any mutes

See merge request pleroma/pleroma!1856

And introduce safe_jsonb_set

Fix hiding branch name logic

See merge request pleroma/pleroma!1845

Fix documentation deploy for stable

See merge request pleroma/pleroma!1844