feat(RemoteActor): add bio, banner_url, followers_url, following_url, also_known_as fields
Bump to 0.3.1. These fields are available on DbActor at follow/ingest time but were discarded when constructing RemoteActor. Now populated in from_json and follow(), so consuming repos can store and return rich actor profiles without extra queries.
This commit is contained in:
20
CHANGELOG.md
20
CHANGELOG.md
@@ -1,6 +1,24 @@
|
||||
# Changelog
|
||||
|
||||
## [0.3.0] — unreleased
|
||||
## [0.3.1] — 2026-05-29
|
||||
|
||||
### Breaking changes
|
||||
|
||||
**`RemoteActor` has five new required fields** — struct literals must include them:
|
||||
|
||||
| Field | Type | Description |
|
||||
|-------|------|-------------|
|
||||
| `bio` | `Option<String>` | Actor biography/summary |
|
||||
| `banner_url` | `Option<String>` | Banner/header image URL |
|
||||
| `followers_url` | `Option<String>` | AP followers collection URL |
|
||||
| `following_url` | `Option<String>` | AP following collection URL |
|
||||
| `also_known_as` | `Vec<String>` | Account aliases (for Move verification) |
|
||||
|
||||
These are populated automatically when k-ap fetches a remote actor (via `from_json`) and when the local `follow()` method constructs a `RemoteActor` from the fetched `DbActor`. Consuming applications only need to add the new fields to their `upsert_remote_actor` / `get_remote_actor` SQL and any custom `RemoteActor` construction sites.
|
||||
|
||||
---
|
||||
|
||||
## [0.3.0] — 2026-05-28
|
||||
|
||||
### Breaking changes
|
||||
|
||||
|
||||
Reference in New Issue
Block a user