Age | Commit message (Collapse) | Author |
|
|
|
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
|
|
|
|
|
|
object in an activity
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.
|
|
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
|
|
|
|
|
|
Final 1.1 release preparations
See merge request pleroma/pleroma!1843
|
|
|
|
Backport/1.1 branch name change
See merge request pleroma/pleroma!1841
|
|
|
|
|
|
message
|
|
|
|
Backport mediaproxy failure tracking enchancements to maint
See merge request pleroma/pleroma!1837
|
|
Make MediaProxy failure tracking less brutal
See merge request pleroma/pleroma!1836
(cherry picked from commit 930cbd6d05653033e9f6d16960d698f5db4ae624)
9bdbf081 Make MediaProxy failure tracking less brutal
|
|
Backport pleroma-ctl enchancements to maint
See merge request pleroma/pleroma!1833
|
|
pleroma_ctl: Make it possible to specify branches/flavours when updating
See merge request pleroma/pleroma!1832
(cherry picked from commit 44afe4c8870d14ae2cd22ff5cfa04555cf5907bd)
b750135a pleroma_ctl: Make it possible to specify branches/flavours when updating
|
|
mastodon api: fix exclude_replies (closes #1287)
See merge request pleroma/pleroma!1816
|
|
|