v2.0.6

What's Changed

• Update docker image to address some CVEs by @mhamzahkhan in #97
• deps: Update dependencies, go version by @yukimochi in #98

Full Changelog: v2.0.5...v2.0.6

v2.0.5

Other Changes

• Update dependencies
• Prepare to use context

v2.0.4

Other Changes

• Update dependencies.

v2.0.3

Other Changes

• Update dependencies.

v2.0.2

Bug fix

• Align all error formats to https://<domain>/inbox: <reason to failed> #82

v2.0.1

Bug fix

• Unwrap innerActivity, innerObject safer #80
  • Nested objects with invalid styles could cause the application to panic.

v2.0.0

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:[email protected] (replacing [email protected]). Result does not have keys 'activity_id' and 'actor_id' (only has 'inbox_url').

v2.0.0rc1

NOTICE: Not well tested, not stable.

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:[email protected] (replacing [email protected]). Result does not have keys 'activity_id' and 'actor_id' (only has 'inbox_url').

v2.0.0beta2

NOTICE: Not well tested, not stable.

v2.0.0beta1

NOTICE: Not well tested, not stable.