Skip to content

v2.0.0

Compare
Choose a tag to compare
@yukimochi yukimochi released this 02 Mar 13:35
· 27 commits to master since this release

New feature

  • Now Activity-Relay can followed by Pleroma and their forks
    • Support Relaying with LitePub Relay Style

Breaking Changes

  • create-as-announce feature removed
    • This configuration is ignored after an upgrade.
  • control config import command accepts a JSON string instead of a json file path.
  • control config enable -d (disable) is replaced by control config disable
  • control domain set -u (undo) is replaced by control domain unset

Migration Notice

Activity-Relay v2.x.x has some breaking changes. You need to check this guide to success upgrade properly.

What version you CURRENTRY running Activity-Relay?

~ v1.1.2, <v1.2.0 (v1.2.0 Release Date: Nov 23, 2022)

Problem

Worker's queue name changed in v1.2.0, but until v1.2.6 there was a task drop feature for tasks with the old queue name.
In v2.0.0 this feature has been removed. Tasks with the old queue name will not be deleted.

Solution

  • Please upgrade to v1.2.0 or above (not include v2.0.0). and run the worker for a while.

What version you START running Activity-Relay?

~ v0.1.1, <v0.2.0 (v0.2.0 Release Date: Dec 9, 2018)

The Redis schema has changed in v0.2.0, but remains backwards compatible up to v1.2.6.
No longer compatible with new features.

Solution

If your relay server has subscribers that following on ~v0.1.1, you'll need to request a refollow.

How to know such subscriber?

Using the Redis CLI, run hgetall relay:subscription:example@example.com (replacing example@example.com). Result does not have keys 'activity_id' and 'actor_id' (only has 'inbox_url').