Repository navigation
Released on November 17, 2026.
@fedify/fedify
- Fixed
Context.sendActivity()andInboxContext.forwardActivity()giving up on the remaining deliveries when one recipient failed. The immediate delivery paths now wait for every delivery they have already started before propagating the error, so the remaining recipients are still reached on runtimes such as Cloudflare Workers, which may terminate an isolate once the error response is returned. This applies both toimmediate: trueand to federations without an outbox queue. [#1380, #1388] - Fixed
CryptoKeyandCryptoKeyPairvalues obtained fromnode:cryptobeing rejected byActorKeyPairsDispatcher,SharedInboxKeyDispatcher,SenderKeyPair,signRequest(),createProof(),signObject(),createSignature(),signJsonLd(),exportJwk(), and the authenticated document loader APIs when@types/node24.7.0 or later is installed. Those APIs now accept a structural key type that both Node.js and DOM/Web Worker keys satisfy, while the keys returned by Fedify keep the ambientCryptoKeytypes.SenderKeyPairandSharedInboxKeyDispatchertake a type parameter that defaults toCryptoKey, so code that reads a key pair or calls a dispatcher keeps the narrower type. [#554, #1391] - Fixed Linked Data Signature verification rejecting documents with unmapped extension properties, such as an undefined
quoteUri, that the sender's JSON-LD processor discards. Discarded properties are not authenticated by the signature. Outbound signing still rejects lossy input, and verification continues to reject relative IRIs and unsafe graph structures. [#1405, #1411] - Fixed Linked Data Signatures being emitted with a JSON-LD context that no longer resolves. The attached
signatureobject now useshttps://w3id.org/security/v1instead ofhttps://w3id.org/identity/v1, which redirects to an unreachable host. Documents signed throughsignJsonLd()orattachSignature()whose context does not definesignaturenow also get a minimal inline definition of that term, so the signed document remains valid JSON-LD. Documents that already carry aproofare left unchanged, since a new context definition would invalidate the proof. Activities queued for fanout before the upgrade also keep their original proof-covered JSON when replayed. Incoming signatures that still useidentity/v1continue to verify. [#664] - Fixed automatic queue worker startup failures becoming unhandled promise rejections. When
manuallyStartQueuewas leftfalseand aMessageQueueimplementation could not start listening, such asWorkersMessageQueueon Cloudflare Workers whoselisten()throws aTypeError, the rejection from the implicit startup in inbox handling and inContext.sendActivity()was discarded. It is now logged as a warning once perFederationinstance, and a synchronous throw from one queue no longer prevents the remaining queues from starting. The failed worker is not retried, so restart the process after fixing the queue.Federation.startQueue()still rejects so callers that start workers deliberately see the error, and Cloudflare Workers deployments should setmanuallyStartQueue: trueto avoid the warning entirely. [#1381, #1390] - Fixed inbox handling that treated valid date-times without seconds, such as
2024-01-01T10:00Zor2024-01-01T10:00.5Z, as permanently malformed. Activity Streams 2.0 allows seconds to be omitted, so activities with such date-times are no longer rejected or dropped. Activities whoseQuestion.closedis a date-like but impossible value, such as2024-02-31T10:00.5Z, are now treated as malformed instead of being accepted withcloseddiscarded. [#1339, #1347 by ChanHaeng Lee] - Fixed incoming Linked Data Signatures without a
createdfield being treated as unsigned. ValidRsaSignature2017signatures without that field now verify through the JSON-LD APIs and inbox, including queued inbox processing, and are forwarded whenskipIfUnsignedis enabled. Malformed signature objects now produce a debug log with their property names. Invalid creator URLs now fail verification without throwing an exception. Outgoing signatures still includecreated. [#1406, #1413] - Fixed singleton
attachmentvalues being serialized as objects in actor, object, and collection responses, which caused Mastodon to ignore a single profile field. Served responses and newly generated activity deliveries now preserve attachment arrays when the JSON-LD context permits it. Documents containing existing proofs or Linked Data signatures are left unchanged by the compatibility rewrite. New normalized deliveries are signed over the same JSON used for queueing and transport. [#1421, #1422, mastodon/mastodon#41640] - Fixed the fanout worker never starting when the
fanoutqueue was the only configured queue.Federation.startQueue()returned without callingfanoutQueue.listen(), so fanout messages were enqueued but never consumed; the implicit startup triggered by a fanout enqueue silently did nothing. Both paths now start the fanout worker, and deployments that configure onlyqueue: { fanout: ... }no longer need to add an unusedinboxoroutboxqueue to make fanout delivery work. [#1389, #1392] - Limited WebFinger lookups made through federation contexts to 10 seconds per lookup. [GHSA-9pmv-w936-hj3f]
- Limited each outgoing activity delivery attempt to 30 seconds, including redirects and HTTP signature retries, so a slow remote inbox cannot hold a delivery worker indefinitely. Timed-out attempts follow the configured retry schedule. [GHSA-fq5h-gjhp-g75x]
- NodeInfo lookups now stop following a redirect when its target repeats an earlier URL in the same chain. A self-redirect previously opened five fetch sessions before hitting the redirect limit; it now stops after the first response. The existing redirect limit still applies to chains without cycles. [GHSA-64hq-2hgr-q4pm]
- NodeInfo lookups now time out after 10 seconds by default. A remote server could previously keep
getNodeInfo()orContext.lookupNodeInfo()waiting indefinitely by delaying a response. The limit covers discovery, redirects, and the document body as one operation. Pass atimeoutvalue in milliseconds to allow more time, ornullto disable the limit; a timed-out lookup returnsundefined. An optionalsignalcan cancel the lookup, even withtimeout: null. [GHSA-64hq-2hgr-q4pm] - On Node.js, NodeInfo hostname resolution now starts at most two operating system DNS lookups at a time. Other hosts can still resolve when one resolver call stalls. A queued lookup can time out or be cancelled before starting, so repeated abandoned NodeInfo requests cannot fill the shared libuv thread pool. An already-running operating system lookup cannot be cancelled. [GHSA-64hq-2hgr-q4pm]
- Fixed
signObject()and the default activity transformers,autoIdAssigner()andactorDehydrator(), dropping the default FEP-ef61 portable object verifier of the object they returned a copy of. Their results now keep the verifier, so their accessors verify portable objects as the original object's accessors do, and they no longer log the warning thatclone()logs when it drops the verifier. [#1399, #1442]
@fedify/backfill
- Fixed backfill accepting
documentLoaderresults with spoofed origins. Results whose declared ID origin differs from the requested IRI's origin are now ignored, including otherwise valid cross-origin redirects. Custom loaders must still validate IDs against the final response URL: pass custom JSON-LD loaders throughlookupObject()and setdocumentUrlto the final response URL after redirects. [GHSA-h3jv-px69-2gpj] - Fixed backfill trusting cross-origin embedded objects, which allowed a remote document to spoof content from another origin. Backfill now dereferences these objects by their IDs before yielding them. It also ignores a
documentLoaderresult whose ID has a different origin from the requested IRI. Consequently, objects reached through a cross-origin redirect are ignored. Custom loaders should pass their JSON-LD loader tolookupObject()so it can validate the object's ID against the final response URL. Backfilled objects remain unverified remote data and should be authenticated before they are persisted or otherwise trusted. [GHSA-x58x-xx7h-7rh4]
@fedify/cli
- The
fedify nodeinfocommand now accepts-T/--timeoutin seconds. It defaults to 10 seconds and reports a timeout separately from a missing or invalid NodeInfo document. [GHSA-64hq-2hgr-q4pm]
@fedify/nestjs
- Fixed
require("@fedify/nestjs")failing withMODULE_NOT_FOUND, which broke the integration in NestJS projects compiled to CommonJS, the NestJS default. The package manifest pointed its CommonJS entry point and type declarations at files that the build no longer produced; they now point to the files that are actually shipped, so the integration loads withrequire()again and TypeScript finds its declarations. ESM imports were not affected. [#1424, #1428]
@fedify/next
- Fixed
fedifyWith()not forwarding NodeInfo document requests such asGET /nodeinfo/2.1without federation media types in their headers.isNodeInfoRequest()andisFederationRequest()now recognize paths under/nodeinfo/regardless of their headers, so clients usingAccept: application/json,*/*, or noAcceptheader can reach the dispatcher. Existing applications must also add{ source: "/nodeinfo/:path*" }to thematcherin their middleware.ts or proxy.ts. Dispatchers outside/nodeinfo/still require explicit delegation tointegrateFederation()and a matchingmatcherentry. [#1402, #1412]
@fedify/testing
- Fixed
MockFederation.receiveActivity()dropping the default FEP-ef61 portable object verifier of the received activity when it attaches its document loaders to the activity passed to inbox listeners. [#1399, #1442]
@fedify/vocab
- Added a warning when
clone()drops the default FEP-ef61 portable object verifier of a vocabulary object, and documented thatclone()does not inherit it. Objects that Fedify parses for you, such as activities that inboxes receive and the results ofContext.lookupObject(), haveContext.verifyPortableObjectas their default, so an existing application that clones them now logs a warning in the["fedify", "vocab", "portable"]category. A clone without a verifier does not verify the portable objects embedded in it, and refuses to dereference portable references. PassverifyPortableObject: ctx.verifyPortableObjecttoclone()to keep verifying them, orverifyPortableObject: undefinedto drop the verifier deliberately without the warning. TheverifyPortableObjectoption ofclone()now explicitly acceptsundefined, so that the opt-out also type-checks withexactOptionalPropertyTypes. [#1399, #1442] - Fixed
CryptographicKeyandMultikeyrejecting apublicKeyobtained fromnode:cryptoin their constructors andclone()when@types/node24.7.0 or later is installed. The property accepts a structural key type now, while the getters still return the ambientCryptoKeytype. [#554, #1391] - Fixed an origin-check bypass that allowed crafted JSON-LD without a parent
idto return forged embedded objects claiming another origin. [GHSA-r388-57j3-5fgp] - Fixed invalid JSON-LD when a collection page embeds a parsed item whose context redefines a protected parent term, such as
proof. Default serialization now isolates independent child contexts while preserving their cached documents and extension meanings. The parent's@contextarray gains property-scoped definitions, including for generated children with matching contexts; context-aware consumers need JSON-LD 1.1 support. Resolving the parent context usescontextLoader; URL references alongside isolated children are represented as objects withidand their own context. [#1394, #1397] - Fixed parsing of date-times without seconds, such as
2024-01-01T10:00Z,2024-01-01T10:00+09:00, or2024-01-01T10:00.5Z, which Activity Streams 2.0 allows. They raised aRangeError, or were ignored inQuestion.closedwhen they had a fraction. Date-like but impossible values inQuestion.closed, such as2024-02-31T10:00.5Z, now raise aRangeErrorinstead of being silently dropped. [#1339, #1347 by ChanHaeng Lee] - Limited WebFinger lookups used by object resolution to 10 seconds each, and actor handle resolution to one 10-second deadline across alias checks. Actor handle resolution now checks at most 100 subject/alias candidates and skips duplicates. [GHSA-9pmv-w936-hj3f]
- Replaced https://w3id.org/identity/v1 with https://w3id.org/security/v1 in the default JSON-LD contexts of activity types. The former no longer resolves, and https://w3id.org/security/v1 defines the same terms the signatures use. [#664, #1351]
@fedify/vocab-runtime
- Added
normalizeDateTimeLiteral()to@fedify/vocab-runtime/temporalso that generated vocabulary code and@fedify/fedifyinterpretxsd:dateTimeliterals the same way. It treats a literal without a UTC offset as UTC and handles literals without seconds, including those with a fraction. [#1339, #1347 by ChanHaeng Lee] - Added the
CryptoKeyLikeandCryptoKeyPairLiketypes for the structural key shape that Fedify APIs accept. They cover keys from Node.js, DOM/Web Workers, and Cloudflare Workers, soexportSpki(),exportMultibaseKey(), andgetAuthenticatedDocumentLoader()no longer reject keys obtained fromnode:cryptowith@types/node24.7.0 or later.AuthenticatedDocumentLoaderFactorykeeps the ambientCryptoKeytype on the identity it receives, so existing implementations do not have to change. [#554, #1391]
@fedify/vocab-tools
- Changed the code generated by
@fedify/vocab-toolsto import theCryptoKeyLiketype from@fedify/vocab-runtime. Regenerated code now requires@fedify/vocab-runtime2.4.6 or later. [#554, #1391] - Fixed generated accessors bypassing origin checks for embedded objects when the parent has no
id. Regenerate your vocabulary code to apply the fix. [GHSA-r388-57j3-5fgp] - Fixed generated default encoders combining independent child documents with conflicting inherited JSON-LD contexts. Child documents retain their original contexts and extension meanings, including in collections and inherited properties. Generated parents gain property-scoped definitions in their
@contextarrays even when child and parent contexts match. Regenerate your vocabulary code to apply the fix. [#1394, #1397] - Fixed generated
xsd:dateTimedecoders failing on date-times without seconds, such as2024-01-01T10:00Zor2024-01-01T10:00.5Z. Regenerate your vocabulary code to get the fix. Generated code now importsnormalizeDateTimeLiteral()from@fedify/vocab-runtime/temporal. [#1339, #1347 by ChanHaeng Lee] - Generated
clone()methods now log a warning in the["fedify", "vocab", "portable"]category when they drop the default FEP-ef61 portable object verifier of the source object, i.e., when the source has one and the call does not pass theverifyPortableObjectoption. An explicitverifyPortableObject: undefineddrops it without the warning. Their API documentation now states thatclone()does not inherit the default verifier. Regenerate custom vocabularies to get the warning. [#1399, #1442]
@fedify/webfinger
- Limited WebFinger lookups to 10 seconds across DNS resolution, redirects, and response reading. A caller's abort signal can end a lookup sooner. This prevents slow endpoints from occupying lookup workers indefinitely. [GHSA-9pmv-w936-hj3f]