Age | Commit message (Collapse) | Author |
|
Bugfix: Elixir 1.14
See merge request pleroma/pleroma!3740
|
|
Bump minimum Elixir version to 1.10
See merge request pleroma/pleroma!3741
|
|
|
|
With the release of Elixir 1.14, Elixir 1.9 is now end-of-life.
Elixir 1.10 Release Notes:
https://github.com/elixir-lang/elixir/releases/tag/v1.10.0
|
|
|
|
Reviewed-on: https://akkoma.dev/AkkomaGang/akkoma/pulls/104
|
|
No migrations or checks yet
|
|
|
|
During attachment upload Pleroma returns a "description" field. Pleroma-fe has an MR to use that to pre-fill the image description field, <https://git.pleroma.social/pleroma/pleroma-fe/-/merge_requests/1399>
* This MR allows Pleroma to read the EXIF data during upload and return the description to the FE
* If a description is already present (e.g. because a previous module added it), it will use that
* Otherwise it will read from the EXIF data. First it will check -ImageDescription, if that's empty, it will check -iptc:Caption-Abstract
* If no description is found, it will simply return nil, just like before
* When people set up a new instance, they will be asked if they want to read metadata and this module will be activated if so
This was taken from an MR i did on Pleroma and isn't finished yet.
|
|
|
|
|
|
Co-authored-by: Egor Kislitsyn <egor@kislitsyn.com>
|
|
Elixir 1.12 changed formatting rules, this allows to avoid having to rollback to run `mix format`
|
|
Backport of: https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3514
|
|
|
|
|
|
old query:
Delete on hashtags (cost=5089.81..5521.63 rows=6160 width=18)
-> Hash Semi Join (cost=5089.81..5521.63 rows=6160 width=18)
Hash Cond: (hashtags.id = ht.id)
-> Seq Scan on hashtags (cost=0.00..317.28 rows=17528 width=14)
-> Hash (cost=5012.81..5012.81 rows=6160 width=20)
-> Merge Anti Join (cost=0.70..5012.81 rows=6160 width=20)
Merge Cond: (ht.id = hto.hashtag_id)
-> Index Scan using hashtags_pkey on hashtags ht (cost=0.29..610.53 rows=17528 width=14)
-> Index Scan using hashtags_objects_pkey on hashtags_objects hto (cost=0.42..3506.48 rows=68158 width=14)
new query:
Delete on hashtags ht (cost=0.70..5012.81 rows=6160 width=12)
-> Merge Anti Join (cost=0.70..5012.81 rows=6160 width=12)
Merge Cond: (ht.id = hto.hashtag_id)
-> Index Scan using hashtags_pkey on hashtags ht (cost=0.29..610.53 rows=17528 width=14)
-> Index Scan using hashtags_objects_pkey on hashtags_objects hto (cost=0.42..3506.48 rows=68158 width=14)
|
|
|
|
|
|
|
|
feature/object-hashtags-rework
|
|
Possibility to run rollback in test env
See merge request pleroma/pleroma!3212
|
|
|
|
feature/object-hashtags-rework
# Conflicts:
# CHANGELOG.md
# lib/mix/tasks/pleroma/database.ex
# lib/pleroma/web/templates/feed/feed/_activity.rss.eex
|
|
For whatever reason it seems to pick up the version without loading the
app on my machine, but not on the CI.
|
|
|
|
migration rollback task changes, hashtags-related config handling tweaks, `hashtags.data` deletion (unused).
|
|
allow user defined text search config in database
See merge request pleroma/pleroma!3275
|
|
priv/repo/optional_migrations/rum_indexing/20190510135645_add_fts_index_to_objects_two.exs files
|
|
|
|
Improve OpenAPI spec and deploy it to api.pleroma.social
See merge request pleroma/pleroma!3296
|
|
Too many changes in OpenAPI spec to describe each one, but
basically it is tag fixes, bringing consitency to operation summaries
and fixing some incorrect information.
|
|
feature/object-hashtags-rework
# Conflicts:
# CHANGELOG.md
# lib/pleroma/web/activity_pub/activity_pub.ex
|
|
data_migration_failed_ids. Added "pleroma.database rollback" task to revert a single migration.
|
|
|
|
|
|
feature/object-hashtags-rework
|
|
|
|
|
|
|
|
feature/object-hashtags-rework
# Conflicts:
# CHANGELOG.md
|
|
Update Oban to 2.3.4
See merge request pleroma/pleroma!3256
|
|
|
|
|
|
Also cosmetic changes to make the code clearer
|
|
|
|
|
|
|
|
|
|
feature/object-hashtags-rework
|