chore(journal): upgrade @fedify/fedify 2.1.16 → 2.2.5
The 2.2.x line was uninstallable when federation landed (@fedify/webfinger@2.2.x wasn't published); fixed upstream, so move to latest. Exact pin stays deliberate — a federation library defines the wire shapes remote instances see. Verified: typecheck, lint, full unit + integration suites (245 tests, including the wire-shape assertions: JRD, actor attachment arrays, PropertyValue fields, dereferenceable Note ids) all green on 2.2.5. Lockfile diff is a clean 24-line swap of the fedify package family. Note: a transient cross-suite flake surfaced when running both integration suites concurrently (shared journal.follows state) — pre-existing, unrelated to the upgrade; clean re-run green. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
7bac3353e0
commit
6fd7329f15
3 changed files with 30 additions and 29 deletions
|
|
@ -1,9 +1,10 @@
|
|||
// ActivityPub federation via Fedify. See openspec/changes/social-federation.
|
||||
//
|
||||
// Version pinning (task 1.2): @fedify/fedify is pinned to exactly 2.1.16.
|
||||
// The whole 2.2.x line is uninstallable from npm — each release depends on
|
||||
// @fedify/webfinger@2.2.x, which was never published (latest is 2.1.16).
|
||||
// Revisit the pin once `pnpm view @fedify/fedify dependencies` resolves.
|
||||
// Version pinning (task 1.2): @fedify/fedify is pinned exactly (no caret).
|
||||
// History: 2.2.x was briefly uninstallable from npm (its @fedify/webfinger
|
||||
// dependency wasn't published) — fixed upstream; upgraded to 2.2.5 on
|
||||
// 2026-06-07. The exact pin stays deliberate: a federation library defines
|
||||
// the wire shapes remote instances see, so upgrades should be conscious.
|
||||
//
|
||||
// Mounting model: Fedify owns URL dispatch for its endpoints via
|
||||
// `federation.fetch(request)`. We delegate to it from React Router routes:
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue