Update dependency @fedify/cli to v1.9.1 #1379
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.7.8->1.9.1Release Notes
fedify-dev/fedify (@fedify/cli)
v1.9.1Compare Source
Released on October 31, 2025.
@fedify/testing
Fixed JSR publishing hanging indefinitely at the processing stage by
hiding complex type exports from the public API. The JSR type analyzer
struggled with complex type dependencies when analyzing the
MockFederation,TestFederation,TestContext, andSentActivitytypes, causing indefinitehangs during the processing stage. [[#468]]
MockFederationclass is no longer exported fromthe public API. Use
createFederation()factory function instead.TestFederation<TContextData>,TestContext<TContextData>, andSentActivityinterfaces are no longer exported from the public API,but their types are still inferred from
createFederation()return typeand can be used via TypeScript's type inference.
@fedify/cli
fedifycommand failing on Windows withPermissionDeniederrorwhen trying to locate or execute package managers during initialization.
The CLI now properly handles *.cmd and *.bat files on Windows by
invoking them through
cmd /c. [[#463]]v1.9.0Compare Source
Released on October 14, 2025.
@fedify/fedify
Implemented FEP-fe34 origin-based security model to protect against
content spoofing attacks and ensure secure federation practices. The
security model enforces same-origin policy for ActivityPub objects and
their properties, preventing malicious actors from impersonating content
from other servers. [#440]
crossOriginoption to Activity Vocabulary property accessors(
get*()methods) with three security levels:"ignore"(default,logs warning and returns
null),"throw"(throws error), and"trust"(bypasses checks).LookupObjectOptions.crossOriginoption tolookupObject()function and
Context.lookupObject()method for controllingcross-origin validation.
and only trusted when they share the same origin or are explicitly
marked as trusted.
performing remote fetches when embedded objects have different origins.
object lifecycles (construction, cloning, and property access).
Added
withIdempotency()method to configure activity idempotencystrategies for inbox processing. This addresses issue #441 where
activities with the same ID sent to different inboxes were incorrectly
deduplicated globally instead of per-inbox. [#441]
IdempotencyStrategytype.IdempotencyKeyCallbacktype.InboxListenerSetters.withIdempotency()method."per-origin"strategy is used for backward compatibility.This will change to
"per-inbox"in Fedify 2.0. We recommendexplicitly setting the strategy to avoid unexpected behavior changes.
Fixed handling of ActivityPub objects containing relative URLs. The
Activity Vocabulary classes now automatically resolve relative URLs by
inferring the base URL from the object's
@idor document URL, eliminatingthe need for manual
baseUrlspecification in most cases. This improvesinteroperability with ActivityPub servers that emit relative URLs in
properties like
icon.urlandimage.url. [#411, #443 by Jiwon Kwon]Added TypeScript support for all RFC 6570 URI Template expression types
in dispatcher path parameters. Previously, only simple string expansion
(
{identifier}) was supported in TypeScript types, while the runtimealready supported all RFC 6570 expressions. Now TypeScript accepts all
expression types including
{+identifier}(reserved string expansion,recommended for URI identifiers),
{#identifier}(fragment expansion),{.identifier}(label expansion),{/identifier}(path segments),{;identifier}(path-style parameters),{?identifier}(query component),and
{&identifier}(query continuation). [#426, #446 by Jiwon Kwon]Rfc6570Expression<TParam>type helper.expressions:
setActorDispatcher(),setObjectDispatcher(),setInboxDispatcher(),setOutboxDispatcher(),setFollowingDispatcher(),setFollowersDispatcher(),setLikedDispatcher(),setFeaturedDispatcher(),setFeaturedTagsDispatcher(),setInboxListeners(),setCollectionDispatcher(), andsetOrderedCollectionDispatcher().Added inverse properties for collections to Vocabulary API.
[FEP-5711, #373, #381 by Jiwon Kwon]
new Collection()constructor now acceptslikesOfoption.Collection.likesOfIdproperty.Collection.getLikesOf()method.new Collection()constructor now acceptssharesOfoption.Collection.sharedOfIdproperty.Collection.getSharedOf()method.new Collection()constructor now acceptsrepliesOfoption.Collection.repliesOfIdproperty.Collection.getRepliesOf()method.new Collection()constructor now acceptsinboxOfoption.Collection.inboxOfIdproperty.Collection.getInboxOf()method.new Collection()constructor now acceptsoutboxOfoption.Collection.outboxOfIdproperty.Collection.getOutboxOf()method.new Collection()constructor now acceptsfollowersOfoption.Collection.followersOfIdproperty.Collection.getFollowersOf()method.new Collection()constructor now acceptsfollowingOfoption.Collection.followingOfIdproperty.Collection.getFollowingOf()method.new Collection()constructor now acceptslikedOfoption.Collection.likedOfIdproperty.Collection.getLikedOf()method.Changed how
parseSoftware()function handles non-Semantic Versioningnumber strings on
tryBestEffortmode. [#353, #365 by Hyeonseo Kim]Separated modules from
@fedify/fedify/xinto dedicated packages toimprove modularity and reduce bundle size. The existing integration
functions in
@fedify/fedify/xare now deprecated and will be removed inversion 2.0.0. [#375 by Chanhaeng Lee]
@fedify/fedify/x/cfworkersin favor of@fedify/cfworkers.@fedify/fedify/x/denokvin favor of@fedify/denokv.@fedify/fedify/x/honoin favor of@fedify/hono.@fedify/fedify/x/sveltekitin favor of@fedify/sveltekit.Extended
Linkfrom@fedify/fedify/webfingerto supportOStatus 1.0 Draft 2. [#402, #404 by Hyeonseo Kim]
templatefield to theLinkinterface.hreffield optional from theLinkinterface according toRFC 7033 Section 4.4.4.3.
Added
Federatable.setWebFingerLinksDispatcher()method to set additionallinks to WebFinger. [#119, #407 by HyeonseoKim]
Added CommonJS support alongside ESM for better NestJS integration and
broader Node.js ecosystem compatibility. This eliminates the need for
Node.js's
--experimental-require-moduleflag and resolves dual packagehazard issues. [#429, #431]
@fedify/cli
Added
Next.jsoption tofedify initcommand. This option allows usersto initialize a new Fedify project with Next.js integration.
[#313 by Chanhaeng Lee]
Changed how
fedify nodeinfocommand handles non-Semantic Versioningnumber strings on
-b/--best-effortmode. Now it uses the same logic asthe
parseSoftware()function in the @fedify/fedify package, whichallows it to parse non-Semantic Versioning number strings more flexibly.
[#353, #365 by Hyeonseo Kim]]
Added
-T/--timeoutoption tofedify lookupcommand. This option allowsusers to specify timeout in seconds for network requests to prevent
hanging on slow or unresponsive servers.
[[#258], #372 by Hyunchae Kim]
@fedify/amqp
CommonJS-based Node.js applications. [#429, #431]
@fedify/cfworkers
Separated from
@fedify/fedify/x/cfworkersto improve modularity andreduce bundle size. [#375 by Chanhaeng Lee]
@fedify/denokv
Separated from
@fedify/fedify/x/denokvto improve modularity andreduce bundle size. [#375 by Chanhaeng Lee]
@fedify/elysia
CommonJS-based Node.js applications. [#429, #431]
@fedify/express
CommonJS-based Node.js applications. [#429, #431]
@fedify/fastify
Created Fastify integration as the @fedify/fastify package.
[#151, #450 by An Subin]
fedifyPlugin()function for integrating Fedify into Fastifyapplications.
Request/Response.@fedify/h3
CommonJS-based Node.js applications. [#429, #431]
@fedify/hono
Created Hono integration as the @fedify/hono package.
Separated from
@fedify/fedify/x/honoto improve modularity andreduce bundle size. [#375 by Chanhaeng Lee]
Added CommonJS support alongside ESM for better compatibility with
CommonJS-based Node.js applications. [#429, #431]
@fedify/koa
Created Koa integration as the @fedify/koa package. [#454, #455]
createMiddleware()function for integrating Fedify into Koaapplications.
Request/Response.
@fedify/next
Created Next.js integration as the @fedify/next package.
[#313 by Chanhaeng Lee]
Added CommonJS support alongside ESM for better compatibility with
CommonJS-based Node.js applications. [#429, #431]
@fedify/postgres
CommonJS-based Node.js applications. [#429, #431]
@fedify/redis
Added support for Redis Cluster to the @fedify/redis package.
[#368 by Michael Barrett]
Added CommonJS support alongside ESM for better compatibility with
CommonJS-based Node.js applications. [#429, #431]
@fedify/sqlite
CommonJS-based Node.js applications. [#429, #431]
@fedify/sveltekit
Created SvelteKit integration as the @fedify/sveltekit package.
Separated from
@fedify/fedify/x/sveltekitto improve modularity andreduce bundle size. [#375 by Chanhaeng Lee]
Fixed SvelteKit integration hook types to correctly infer the request
and response types in hooks. [#271, #394 by Chanhaeng Lee]
Added CommonJS support alongside ESM for better compatibility with
CommonJS-based Node.js applications. [#429, #431]
@fedify/testing
CommonJS-based Node.js applications. [#429, #431]
v1.8.14Compare Source
Released on October 19, 2025.
@fedify/testing
The issue was caused by TypeScript function overload signatures in
MockContextandMockFederationclasses that triggered a bug in JSR'stype analyzer. All method overloads have been removed and simplified to
use
anytypes where necessary. [#468, #470]@fedify/cli
fedifycommand failing on Windows withPermissionDeniederrorwhen trying to locate or execute package managers during initialization.
The CLI now properly handles *.cmd and *.bat files on Windows by
invoking them through
cmd /c. [#463]v1.8.13Compare Source
Released on October 10, 2025.
@fedify/fedify
special characters. Updated uri-template-router to version 1.0.0,
which properly decodes percent-encoded characters in URI template variables
according to RFC 6570. This resolves issues where identifiers containing
URIs (e.g.,
https%3A%2F%2Fexample.com) were being inconsistently decodedin dispatcher callbacks and double-encoded in collection URLs. [#416]
v1.8.12Compare Source
Released on September 20, 2025.
@fedify/sqlite
included in the bundled output. The @js-temporal/polyfill dependency
was moved from
devDependenciestodependenciesto ensure properbundling.
v1.8.11Compare Source
Released on September 17, 2025.
edge cases. The fix now properly percent-encodes any authority component
in
at://URIs, supportingdid:web,did:key, and other DID methodsbeyond just
did:plc. Also handles URIs without path componentscorrectly. [[#436]]
v1.8.10Compare Source
Released on September 17, 2025.
@fedify/fedify
URIs like
at://did:plc:...that violate RFC 3986 URI syntax are nowautomatically URL-encoded to
at://did%3Aplc%3A...to prevent parsingfailures when processing bridged Bluesky content. [[#436]]
v1.8.9Compare Source
Released on September 10, 2025.
@fedify/express, @fedify/h3, @fedify/nestjs, @fedify/postgres,
@fedify/redis, @fedify/sqlite, @fedify/testing) now specify explicit
version ranges for the @fedify/fedify peer dependency instead of
accepting any version, improving compatibility guarantees.
v1.8.8Compare Source
Released on August 25, 2025.
@fedify/fedify
verifyRequest()function threw aTypeErrorwhenverifying HTTP Signatures with
createdorexpiresfields inthe
Signatureheader as defined in draft-cavage-http-signatures-12,causing
500 Internal Server Errorresponses in inbox handlers.Now it correctly handles these fields as unquoted integers according
to the specification.
v1.8.7Compare Source
Released on August 25, 2025.
@fedify/fedify
self-closing
<link>tags. The HTML/XHTML parser now correctly handleswhitespace before the self-closing slash (
/>), improving compatibilitywith XHTML documents that follow the self-closing tag format.
v1.8.6Compare Source
Released on August 24, 2025.
@fedify/nestjs
ActivityPub requests in NestJS applications. The middleware now correctly
handles request bodies that have been pre-processed by other NestJS
middleware or interceptors. [#279, #386 by Jaeyeol Lee]
@fedify/testing
Updated exports to include context creation functions.
[#382 by Colin Mitchell]
createContext()function.createInboxContext()function.createRequestContext()function.v1.8.5Compare Source
Released on August 8, 2025.
@fedify/fedify
that allowed unauthenticated attackers to impersonate any ActivityPub actor.
The vulnerability occurred because activities were processed before
verifying that the HTTP Signatures key belonged to the claimed actor.
Now authentication verification is performed before activity processing to
prevent actor impersonation attacks. [[CVE-2025-54888]]
@fedify/cli
fedify nodeinfocolor support in Windows Terminal.[#358, #360 by KeunHyeong Park]
v1.8.4Compare Source
Released on August 7, 2025.
@fedify/cli
fedify lookupcommand's-r/--raw,-C/--compact, and-e/--expandoptions to properly output valid JSON format instead ofDeno's object inspection format. [#357]
v1.8.3Compare Source
Released on August 6, 2025.
@fedify/cli
Restored image resizing functionality in
fedify lookupcommand by usingthe existing Jimp library for image manipulation. This properly displays
iconandimagefields with appropriate sizing in terminals.Added support for Ghostty terminal emulator for image rendering in
fedify lookupcommand.v1.8.2Compare Source
Released on August 6, 2025.
@fedify/cli
Fixed
npx @​fedify/clicommand not working on various platforms bycorrecting the binary path resolution in the Node.js wrapper script.
Temporarily removed Sharp dependency to resolve installation issues
across different platforms. As a result,
fedify lookupcommand will nolonger resize images when displaying them in the terminal. This is a
temporary workaround and image resizing functionality will be restored
in a future patch version using an alternative approach.
Fixed build artifact paths in GitHub Actions workflow to correctly
reference CLI package location in the monorepo structure.
v1.8.1Compare Source
Released on October 19, 2025.
@fedify/testing
The issue was caused by TypeScript function overload signatures in
MockContextandMockFederationclasses that triggered a bug in JSR'stype analyzer. All method overloads have been removed and simplified to
use
anytypes where necessary. [#468, #470]@fedify/cli
fedifycommand failing on Windows withPermissionDeniederrorwhen trying to locate or execute package managers during initialization.
The CLI now properly handles *.cmd and *.bat files on Windows by
invoking them through
cmd /c. [#463]v1.7.13Compare Source
Released on September 17, 2025.
edge cases. The fix now properly percent-encodes any authority component
in
at://URIs, supportingdid:web,did:key, and other DID methodsbeyond just
did:plc. Also handles URIs without path componentscorrectly. [[#436]]
v1.7.12Compare Source
Released on September 17, 2025.
URIs like
at://did:plc:...that violate RFC 3986 URI syntax are nowautomatically URL-encoded to
at://did%3Aplc%3A...to prevent parsingfailures when processing bridged Bluesky content. [[#436]]
v1.7.11Compare Source
Released on August 25, 2025.
verifyRequest()function threw aTypeErrorwhenverifying HTTP Signatures with
createdorexpiresfields inthe
Signatureheader as defined in draft-cavage-http-signatures-12,causing
500 Internal Server Errorresponses in inbox handlers.Now it correctly handles these fields as unquoted integers according
to the specification.
v1.7.10Compare Source
Released on August 25, 2025.
self-closing
<link>tags. The HTML/XHTML parser now correctly handleswhitespace before the self-closing slash (
/>), improving compatibilitywith XHTML documents that follow the self-closing tag format.
v1.7.9Compare Source
Released on August 8, 2025.
that allowed unauthenticated attackers to impersonate any ActivityPub actor.
The vulnerability occurred because activities were processed before
verifying that the HTTP Signatures key belonged to the claimed actor.
Now authentication verification is performed before activity processing to
prevent actor impersonation attacks. [[CVE-2025-54888]]
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - Between 08:00 AM and 11:59 AM, only on Monday, Tuesday, Wednesday, and Thursday ( * 8-11 * * 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.