Update dependency @fedify/hono to v1.10.3#1490
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
4e6489e to
3e39cb6
Compare
3e39cb6 to
b7ef735
Compare
b7ef735 to
8e67481
Compare
8e67481 to
e880f59
Compare
e880f59 to
7f1b8ec
Compare
7f1b8ec to
8bd1279
Compare
8bd1279 to
854d5eb
Compare
854d5eb to
88bce9d
Compare
88bce9d to
698ece9
Compare
698ece9 to
0bb70f7
Compare
0bb70f7 to
a06343f
Compare
|
@codex review |
There was a problem hiding this comment.
Pull request overview
This PR updates the @fedify/hono package from version 1.9.1 to 1.10.3, which is an integration package for using Fedify with the Hono web framework. The update spans multiple minor versions (1.10.0, 1.10.1, 1.10.2, 1.10.3) and includes bug fixes in the Fedify ecosystem, particularly for @fedify/testing methods and traverseCollection() functionality.
Changes:
- Updated
@fedify/honodependency from 1.9.1 to 1.10.3 in package.json - Updated corresponding yarn.lock entries with new version, resolved URL, and integrity hash
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| package.json | Updated @fedify/hono dependency version from 1.9.1 to 1.10.3 |
| yarn.lock | Updated lock file entries for @fedify/hono with new version metadata |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "@fedify/fedify": "1.9.1", | ||
| "@fedify/hono": "1.9.1", | ||
| "@fedify/hono": "1.10.3", | ||
| "@fedify/redis": "1.9.1", |
There was a problem hiding this comment.
Potential version mismatch detected. The @fedify/hono package is being updated to version 1.10.3, but @fedify/fedify remains at version 1.9.1. These packages are part of the same monorepo (fedify-dev/fedify) and the release notes show that version 1.10.0 introduced significant changes including new interfaces (KvStore.list(), FedifySpanExporter) and OpenTelemetry enhancements.
The @fedify/redis package (version 1.9.1) and @fedify/cli package (version 1.9.1 in devDependencies) are also out of sync with @fedify/hono.
Consider updating all @fedify/* packages to the same version (1.10.3 or at least 1.10.x) to ensure compatibility. The release notes indicate that version 1.10.x includes features like the new optional list() method in the KvStore interface that was implemented across all KvStore implementations (including RedisKvStore, which this project uses).
|
Codex Review: Didn't find any major issues. Delightful! ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@package.json`:
- Around line 66-68: The package.json pins `@fedify/fedify` to 1.9.1 which
conflicts with `@fedify/hono`'s peerDependency requirement; update the dependency
entry "@fedify/fedify" to at least "1.10.3" (or a matching semver like
"^1.10.3") and run dependency checks/build/tests to ensure `@fedify/redis` and
other packages remain compatible with the bumped `@fedify/fedify`.
| "@fedify/fedify": "1.9.1", | ||
| "@fedify/hono": "1.9.1", | ||
| "@fedify/hono": "1.10.3", | ||
| "@fedify/redis": "1.9.1", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Inspect peer/dependency requirements for `@fedify/hono`@1.10.3
npm view `@fedify/hono`@1.10.3 peerDependencies
npm view `@fedify/hono`@1.10.3 peerDependenciesMeta
npm view `@fedify/hono`@1.10.3 dependencies
npm view `@fedify/hono`@1.10.3 enginesRepository: TryGhost/ActivityPub
Length of output: 111
@fedify/hono 1.10.3 requires @fedify/fedify ≥1.10.3 as a peer dependency, but package.json pins it at 1.9.1.
The peer dependency constraint @fedify/fedify: '^1.10.3' will be violated. Bump @fedify/fedify to at least 1.10.3 and verify @fedify/redis compatibility.
🤖 Prompt for AI Agents
In `@package.json` around lines 66 - 68, The package.json pins `@fedify/fedify` to
1.9.1 which conflicts with `@fedify/hono`'s peerDependency requirement; update the
dependency entry "@fedify/fedify" to at least "1.10.3" (or a matching semver
like "^1.10.3") and run dependency checks/build/tests to ensure `@fedify/redis`
and other packages remain compatible with the bumped `@fedify/fedify`.
a06343f to
8660a80
Compare
This PR contains the following updates:
1.9.1→1.10.3Release Notes
fedify-dev/fedify (@fedify/hono)
v1.10.3Compare Source
Released on February 1, 2026.
@fedify/fedify
traverseCollection()yielding no items when aCollectionhasan inline
CollectionPagein itsfirstproperty without an explicitid. This is common in Mastodon'srepliescollections. The functionpreviously used
collection.firstIdto determine pagination, whichreturned
nullfor inline pages without anid, causing it toincorrectly fall into the non-paginated branch. [#550 by Lee Dogeon]
v1.10.2Compare Source
Released on January 23, 2026.
@fedify/testing
TestContext.getActorKeyPairs()returning empty array instead ofcalling registered key pairs dispatcher. The method now properly invokes
the key pairs dispatcher when it is registered via
setKeyPairsDispatcher(). [#530]v1.10.1Compare Source
Released on January 22, 2026.
@fedify/testing
TestContext.getActor()andTestContext.getObject()returningnullinstead of calling registered dispatchers. The methods now properlyinvoke actor and object dispatchers when they are registered via
setActorDispatcher()andsetObjectDispatcher(). [[#530]]v1.10.0Compare Source
Released on December 24, 2025.
@fedify/fedify
Enhanced OpenTelemetry instrumentation with span events for capturing
detailed activity data. Span events now record complete activity JSON
payloads and verification status, enabling richer observability and
debugging capabilities without relying solely on span attributes
(which only support primitive values). [#323]
activitypub.activity.receivedspan event to theactivitypub.inboxspan, recording the full activity JSON,verification status (activity verified, HTTP signatures verified,
Linked Data signatures verified), and actor information.
activitypub.activity.sentspan event to theactivitypub.send_activityspan, recording the full activity JSONand target inbox URL.
activitypub.object.fetchedspan event to theactivitypub.lookup_objectspan, recording the fetched object'stype and complete JSON-LD representation.
Added OpenTelemetry spans for previously uninstrumented operations:
[#323]
activitypub.fetch_documentspan for document loader operations,tracking URL fetching, HTTP redirects, and final document URLs.
activitypub.verify_key_ownershipspan for cryptographickey ownership verification, recording actor ID, key ID, verification
result, and the verification method used.
Added optional
list()method to theKvStoreinterface for enumeratingentries by key prefix. This method takes an optional
prefixparameter;when omitted or empty, it returns all entries. This enables efficient
prefix scanning which is useful for implementing features like distributed
trace storage, cache invalidation by prefix, and listing related entries.
[#498, #500]
KvStoreListEntryinterface.MemoryKvStore.Added
FedifySpanExporterclass that persists ActivityPub activity tracesto a
KvStorefor distributed tracing support. This enables aggregatingtrace data across multiple nodes in a distributed deployment, making it
possible to build debug dashboards that show complete request flows across
web servers and background workers. [#497, #502]
@fedify/fedify/otelmodule.FedifySpanExporterclass implementing OpenTelemetry'sSpanExporterinterface.TraceActivityRecordinterface for stored activity data,including
actorIdandsignatureDetailsfields for debug dashboardsupport.
SignatureVerificationDetailsinterface for detailed signatureverification information.
TraceSummaryinterface for trace listing.FedifySpanExporterOptionsinterface.GetRecentTracesOptionsinterface.ActivityDirectiontype.@fedify/nestjs
expresspeer dependency range to support NestJS 11.[#492, #493 by Cho Hasang]
@fedify/sqlite
list()method inSqliteKvStore. [#498, #500]@fedify/postgres
list()method inPostgresKvStore. [#498, #500]@fedify/redis
list()method inRedisKvStore. [#498, #500]@fedify/denokv
list()method inDenoKvStore. [#498, #500]@fedify/cfworkers
list()method inWorkersKvStore. [#498, #500]v1.9.5Compare Source
Released on February 1, 2026.
@fedify/fedify
traverseCollection()yielding no items when aCollectionhasan inline
CollectionPagein itsfirstproperty without an explicitid. This is common in Mastodon'srepliescollections. The functionpreviously used
collection.firstIdto determine pagination, whichreturned
nullfor inline pages without anid, causing it toincorrectly fall into the non-paginated branch. [[#550] by Lee Dogeon]
v1.9.4Compare Source
Released on January 23, 2026.
@fedify/testing
TestContext.getActorKeyPairs()returning empty array instead ofcalling registered key pairs dispatcher. The method now properly invokes
the key pairs dispatcher when it is registered via
setKeyPairsDispatcher(). [[#530]]v1.9.3Compare Source
Released on January 22, 2026.
@fedify/testing
TestContext.getActor()andTestContext.getObject()returningnullinstead of calling registered dispatchers. The methods now properlyinvoke actor and object dispatchers when they are registered via
setActorDispatcher()andsetObjectDispatcher(). [[#530]]v1.9.2Compare Source
Released on December 20, 2025.
@fedify/fedify
the document loader's HTML parsing. An attacker-controlled server could
respond with a malicious HTML payload that blocked the event loop.
[CVE-2025-68475]
@fedify/sqlite
SyntaxError: Identifier 'Temporal' has already been declarederrorthat occurred when using
SqliteKvStoreon Node.js or Bun. The errorwas caused by duplicate
Temporalimports during the build process.[#487]
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - Between 07:00 AM and 04:59 PM, only on Monday, Tuesday, Wednesday, and Thursday ( * 7-16 * * 1,2,3,4 ) (UTC).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Never, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.