summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2024-08-21Use Map.filter now that minimum Elixir version is 1.13Mark Felder
2024-08-19Merge branch 'reachability' into 'develop'feld
Fix reachability based on results of publishing attempts See merge request pleroma/pleroma!4231
2024-08-19Merge branch 'remote-fetcher-fixes' into 'develop'feld
Improve Remote Object Fetcher error handling, Oban See merge request pleroma/pleroma!4230
2024-08-19Address case where instance reachability status couldn't be updatedMark Felder
2024-08-19Fix test cases for validating instance reachability based on results of ↵Mark Felder
publishing attempts Now that we store the unreachable_since in the Oban job the value is no longer a %NaiveDateTime{} so the code was wrong
2024-08-18Merge branch 'mogrify' into 'develop'feld
Update mogrify See merge request pleroma/pleroma!4225
2024-08-17Improve Remote Object Fetcher error handling, ObanMark Felder
2024-08-17Merge remote-tracking branch 'origin/develop' into mogrifyMark Felder
2024-08-17Merge branch 'bump-oban' into 'develop'feld
Update Oban to 2.18 See merge request pleroma/pleroma!4228
2024-08-17Update Oban to 2.18Mark Felder
2024-08-16Update mogrifyMark Felder
Sent a pull request upstream to expand the version range depended on my blurhash https://github.com/rinpatch/blurhash/pull/1
2024-08-16Merge branch 'bugfix-truncate-remote-user-fields' into 'develop'feld
User: truncate remote user fields instead of rejecting See merge request pleroma/pleroma!4220
2024-08-16Merge branch 'norifications-marker' into 'develop'feld
Fix 'Setting a marker should mark notifications as read' Closes #2769 See merge request pleroma/pleroma!4223
2024-08-16Merge branch 'ci-git-fetch' into 'develop'feld
CI: GIT_STRATEGY: fetch See merge request pleroma/pleroma!4224
2024-08-15CI: GIT_STRATEGY: fetchHaelwenn (lanodan) Monnier
Seems to avoid fetching all the branches which was preventing shallow cloning from being actually useful.
2024-08-14Fix 'Setting a marker should mark notifications as read'marcin mikołajczak
Signed-off-by: marcin mikołajczak <git@mkljczk.pl>
2024-08-14User: truncate remote user fields instead of rejectingHaelwenn (lanodan) Monnier
2024-08-13Merge branch 'fix-random-test-errors' into 'develop'feld
Fix random test failures, revert auto-retry failed tests See merge request pleroma/pleroma!4221
2024-08-13Revert "Custom mix task to retry failed tests once in CI pipeline"Mark Felder
This reverts commit ed2976b237b53a524247d564691e0a12d3231d68.
2024-08-13Fix the uploads migration mix task test which leaked a change to the ↵Mark Felder
configured Uploader
2024-08-13Merge branch 'mrf-cleanup' into 'develop'feld
MRF cleanup See merge request pleroma/pleroma!4219
2024-08-13MRF cleanupMark Felder
MRFs written over time have been inconsistent with the terminology of what is being processed. MRFs work on Activities, but generally we always named the assignments "message" or "object" which is really confusing when trying to debug or write tests.
2024-08-13Merge branch 'mrf-tests' into 'develop'feld
MRF.FODirectReply: use Visibility module to verify the scope See merge request pleroma/pleroma!4218
2024-08-12MRF.FODirectReply: use Visibility module to verify the scopeMark Felder
2024-08-12MRF.QuietReply: add test for replies to unlisted postsMark Felder
2024-08-12Merge branch 'followers-only-reply-direct-mrf' into 'develop'feld
MRF.FODirectReply See merge request pleroma/pleroma!4091
2024-08-12Merge branch 'user-factory' into 'develop'feld
User Factory: include the nickname in the generated URLs See merge request pleroma/pleroma!4214
2024-08-12Merge branch 'deprecate-subscribe' into 'develop'feld
Mark `/api/v1/pleroma/accounts/:id/subscribe`/`unsubscribe` as deprecated See merge request pleroma/pleroma!4216
2024-08-12User Factory: include the nickname in the generated URLsMark Felder
2024-08-12MRF.FODirectReplyMark Felder
Force replies to followers-only posts to always be direct
2024-08-12Merge branch 'mrf-quietreply' into 'develop'feld
MRF.QuietReply See merge request pleroma/pleroma!4213
2024-08-12Add module documentationMark Felder
2024-08-12Merge branch 'identity-proofs' into 'develop'feld
Remove stub for /api/v1/accounts/:id/identity_proofs (deprecated by Mastodon 3.5.0) See merge request pleroma/pleroma!4215
2024-08-12Merge branch 'swoosh-mailgun' into 'develop'feld
Fix Swoosh Mailgun support See merge request pleroma/pleroma!4217
2024-08-12Revert accidental removal of test unrelated to identity proofsMark Felder
2024-08-12Fix Swoosh Mailgun supportMark Felder
2024-08-12remove unused aliasmarcin mikołajczak
Signed-off-by: marcin mikołajczak <git@mkljczk.pl>
2024-08-12Mark `/api/v1/pleroma/accounts/:id/subscribe`/`unsubscribe` as deprecatedmarcin mikołajczak
Signed-off-by: marcin mikołajczak <git@mkljczk.pl>
2024-08-12Update test as /api/v1/endorsements is not a stubmarcin mikołajczak
Signed-off-by: marcin mikołajczak <git@mkljczk.pl>
2024-08-12Remove stub for /api/v1/accounts/:id/identity_proofs (deprecated by Mastodon ↵marcin mikołajczak
3.5.0) Signed-off-by: marcin mikołajczak <git@mkljczk.pl>
2024-08-08We must change to/cc in the activity and inner objectMark Felder
2024-08-08Unintended commitMark Felder
2024-08-08Added MRF.QuietReply which prevents replies to public posts from being ↵Mark Felder
published to the timelines
2024-08-08Merge branch 'inactive-test' into 'develop'feld
Do not allow committing tests with a .ex extension See merge request pleroma/pleroma!4211
2024-08-08Merge branch 'follow-validator' into 'develop'lain
Do not require a cc field when validating an incoming Follow activity See merge request pleroma/pleroma!4212
2024-08-07Remove validation for cc fields on BlocksMark Felder
2024-08-07Remove validation for cc fields on Follow Accept/RejectMark Felder
2024-08-07Improve variable nameMark Felder
2024-08-07Improve the FollowValidatorMark Felder
2024-08-07Do not require a cc field when validating an incoming Follow activityMark Felder
The cc field is not required and the code was keeping the cc if it existed on an activity or replacing it with the default of an empty list when casting. If any Follow activity was received with a cc field, it would attempt to keep it. This was noticed in !4208 where we would craft Follow requests with a cc value of nil.