• The LanguageString.language property is now LanguageString.locale and is of type Intl.Locale instead of LanguageTag.
• The LanguageString constructor now accepts either an Intl.Locale object or a string for the language parameter.
• The Link.language property is now of type Intl.Locale instead of LanguageTag.
• Removed the @phensley/language-tag dependency.

@fedify/cli

• The Fedify CLI now runs natively on Node.js and Bun without requiring compiled binaries, providing a more natural JavaScript package experience for Node.js and Bun users. [#374, #456, #457]

• Added fedify generate-vocab command to generate Activity Vocabulary classes from schema files. This command uses the new @fedify/vocab-tools package internally and allows users to extend Activity Vocabulary with custom types. [#444, #458 by ChanHaeng Lee]

• Updated fedify init command for better DX. [#397, #435 by Chanhaeng Lee]

  • If the directory is not empty, prompts the user for confirmation before proceeding. If the user agrees, it moves the remaining directory to trash and continue the initialization from new created directory.
  • Ask again if some options is not specified or invalid.

• The fedify lookup command now supports multiple URLs with the -t/--traverse option, allowing users to traverse multiple collections in a single command. [#408, #449 by Jiwon Kwon]

• The fedify init command now supports Elysia as a web framework option, with runtime-specific templates for Deno, Bun, and Node.js environments. [#460, #496 by Hyeonseo Kim]

• Fixed a bug in the fedify init command where Deno import map generation incorrectly handled dependencies with registry prefixes (e.g., npm:), creating invalid specifiers in deno.json. [#460, #496 by Hyeonseo Kim]

• Added fedify relay command to run an ephemeral ActivityPub relay server. [#510, #518 by Jiwon Kwon]

  • Supports both Mastodon and LitePub relay protocols via --protocol option.
  • Provides optional persistent storage via --persistent option with SQLite database.
  • Allows configuring subscription approval/rejection via --accept-follow and --reject-follow options.
  • Tunnels the relay server to the public internet by default for external access, with --no-tunnel option to run locally only.

• Added --tunnel-service option to fedify lookup, fedify inbox, and fedify relay commands to select the tunneling service (localhost.run, serveo.net, or pinggy.io). Also added --tunnel-service as an alias to the existing -s/--service option in fedify tunnel for consistency. [#525, #529, #531 by Jiwon Kwon]

• Added configuration file support for CLI commands. The CLI now loads settings from configuration files at multiple levels, with a well-defined precedence chain. [#555, #566 by Jiwon Kwon]

  • By default, configuration is loaded (in order of increasing precedence) from a system-wide configuration file (/etc/xdg/fedify/config.toml), a user-level configuration file (~/.config/fedify/config.toml), and .fedify.toml in the current directory; later files override earlier ones.
  • Added --config option to specify a custom configuration file path; this file has the highest precedence over all other configuration sources.
  • Added --ignore-config option to skip configuration file loading.
  • All command options (inbox, lookup, webfinger, nodeinfo, tunnel, relay) can now be configured via any of the configuration files.

@fedify/debugger

• Created the @fedify/debugger package, an embedded real-time ActivityPub debug dashboard for Fedify. It wraps an existing Federation object as a proxy, intercepting requests to a configurable path prefix (default /__debug__) and serving an SSR-based web UI. [#561, #564]

  • Added createFederationDebugger() function that returns a Federation proxy with a built-in debug dashboard. When called without an exporter option, it automatically sets up OpenTelemetry tracing (creating MemoryKvStore, FedifySpanExporter, BasicTracerProvider) and registers it as the global tracer provider—no manual OTel configuration needed.
  • Traces list page showing trace IDs, activity types, activity counts, and timestamps, with auto-polling for real-time updates.
  • Trace detail page showing activity direction, type, actor, signature verification details, inbox URL, and expandable activity JSON.
  • JSON API endpoint at /__debug__/api/traces for programmatic access.
  • Added per-trace log collection using LogTape. The returned federation object now includes a sink property (a LogTape Sink function) that captures log records grouped by trace ID. In the simplified overload (without exporter), LogTape is auto-configured.
  • Trace detail page now shows a “Logs” section with log level, timestamp, logger category, and message for each log record in the trace.
  • JSON API endpoint at /__debug__/api/logs/:traceId for retrieving log records for a specific trace.
  • Added optional auth configuration for protecting the debug dashboard with authentication. Supports three modes: password-only, username + password, and request-based (e.g., IP filtering). Each mode supports both static credentials and callback functions. Uses cookie-based sessions with HMAC-signed tokens.

@fedify/relay

• Created ActivityPub relay integration as the @fedify/relay package. [#359, #459, #471, #490, #510, #518 by Jiwon Kwon]

  • Added Relay interface defining the common contract for relay implementations.
  • Added MastodonRelay class implementing Mastodon-compatible relay protocol.
  • Added LitePubRelay class implementing LitePub-compatible relay protocol.
  • Added SubscriptionRequestHandler type for custom subscription approval logic.
  • Added RelayOptions interface for relay configuration.
  • Added RelayType type alias to document the type-safe parameter
  • Added createRelay() factory function as a key public API

@fedify/vocab-tools

• Created Activity Vocabulary code generator as the @fedify/vocab-tools package. Separated vocabulary code generation tools from the main @fedify/fedify package to improve modularity and enable custom vocabulary extensions across different JavaScript runtimes. [#444, #458 by ChanHaeng Lee]

  • Made the code generator runtime-agnostic, supporting Deno, Node.js, and Bun environments.
  • Provides programmatic API for generating vocabulary classes from schema files.
  • Integrated with fedify generate-vocab CLI command.
  • Published to both npm and JSR for broad ecosystem compatibility.

@fedify/vocab-runtime

• Created ActivityPub vocabulary runtime as the @fedify/vocab-runtime package. Separated core vocabulary generation and processing modules from the main @fedify/fedify package to improve modularity and reduce coupling between vocabulary processing and federation functionality. [#444, #451 by ChanHaeng Lee]

  • Extracted DocumentLoader, RemoteDocument, and related types from the main package.
  • Moved cryptographic key processing utilities, e.g., importSpki, exportSpki, importMultibaseKey, exportMultibaseKey.
  • Relocated multibase encoding/decoding functionality.
  • Separated language string processing (LanguageString class).
  • This package is primarily used by generated vocabulary classes and provides the runtime infrastructure for ActivityPub object processing.

@fedify/elysia

• Added deno.json configuration file to enable proper Deno tooling support in the package. [#460, #496]

@fedify/lint

• Created Fedify linting tools as the @fedify/lint package. This package provides shared Deno Lint and ESLint configurations for consistent code style across Fedify packages and user projects. [#297, #494 by ChanHaeng Lee]

@fedify/fresh

• Created a new @fedify/fresh package that provides seamless integration between Fedify and Fresh 2.0, replacing the deprecated @fedify/fedify/x/fresh module that was designed for Fresh 1.x. [#466, #478 by Hyeonseo Kim]

@fedify/webfinger

• Created WebFinger utilities as the @fedify/webfinger package. This package provides tools for working with WebFinger resources, including parsing and generating WebFinger documents. [#517 by ChanHaeng Lee]

@fedify/vocab

• Created ActivityPub Vocabulary API package as the @fedify/vocab package. This package contains the generated Activity Vocabulary classes and related types, separated from the main @fedify/fedify package to improve modularity and enable custom vocabulary extensions. The previous @fedify/fedify/vocab module is now deprecated and re-exports all exports from this package for backward compatibility. [#437, #517 by ChanHaeng Lee]

• @fedify/vocab now re-exports LanguageString, DocumentLoader, GetUserAgentOptions, and RemoteDocument from @fedify/vocab-runtime so that downstream consumers do not need to depend on @fedify/vocab-runtime directly. [#560]

• Fixed @fedify/vocab-runtime being bundled inline into @fedify/vocab's ESM/CJS output instead of being kept as an external dependency. This caused instanceof LanguageString checks to fail because two distinct LanguageString classes existed at runtime. [#560]

@fedify/sqlite

• Added SqliteMessageQueue class implementing MessageQueue interface using SQLite as the backing store. This implementation uses polling to check for new messages and is suitable for single-node deployments and development environments. [#477, #526 by ChanHaeng Lee]

  • Added SqliteMessageQueue class.
  • Added SqliteMessageQueueOptions interface.

• SqliteMessageQueue now supports the orderingKey option to ensure messages with the same ordering key are processed sequentially. [#538, #540]

  • Added ordering_key column to the message queue table schema.
  • The new table schema is created when SqliteMessageQueue.initialize() is called on a fresh database.

@fedify/testing

• Added testMessageQueue() utility function for standardized testing of MessageQueue implementations. This function provides a reusable test harness that covers common message queue operations including enqueue(), enqueue() with delay, enqueueMany(), and multiple listener scenarios. [#477, #526 by ChanHaeng Lee]

  • Added testMessageQueue() function.
  • Added waitFor() helper function.
  • Added getRandomKey() helper function.

• Added TestMessageQueueOptions interface and optional options parameter to testMessageQueue() function. [#538, #540]

  • Added TestMessageQueueOptions interface.
  • Added testOrderingKey option to enable ordering key tests.

@fedify/redis

• Fixed a race condition in RedisMessageQueue.listen() where pub/sub notifications could be missed if enqueue() was called immediately after listen() started. The issue occurred because the message handler was attached inside an async callback, allowing a timing window where messages could be published before the handler was ready. [#515, #532 by Jiwon Kwon]

• RedisMessageQueue now supports the orderingKey option to ensure messages with the same ordering key are processed sequentially. [#538, #540]

@fedify/postgres

• PostgresMessageQueue now supports the orderingKey option to ensure messages with the same ordering key are processed sequentially. [#538, #540]

  • Added ordering_key column to the message queue table schema.
  • The new table schema is created when PostgresMessageQueue.initialize() is called on a fresh database.

• Fixed a race condition in PostgresMessageQueue.initialize() where concurrent calls from listen() and enqueue() would run DDL statements in parallel, causing redundant table creation and ALTER TABLE operations. The initialization promise is now cached so that concurrent callers share the same work.

• Fixed PostgresMessageQueue.listen() spawning many concurrent poll() calls when a burst of NOTIFY signals arrived (e.g., from bulk enqueue of 100 messages), causing excessive database contention. Poll executions are now serialized so that at most one runs at a time, with subsequent requests queued after the current one finishes.

@fedify/amqp

• AmqpMessageQueue now supports the orderingKey option to ensure messages with the same ordering key are processed sequentially. [#538, #540]

  • Uses RabbitMQ's rabbitmq_consistent_hash_exchange plugin to route messages with the same ordering key to the same queue.
  • The plugin must be enabled on the RabbitMQ server for ordering key support to work.

@fedify/cfworkers

• WorkersMessageQueue now supports the orderingKey option to ensure messages with the same ordering key are processed sequentially. [#538, #540]

  • Added WorkersMessageQueueOptions interface with orderingKv, orderingKeyPrefix, and orderingLockTtl options.
  • Added processMessage() method to handle lock acquisition and release.
  • Requires a Workers KV namespace for lock management.
  • Due to Workers KV eventual consistency, ordering is best-effort.

@fedify/init

• Created project initializer as the @fedify/init package. Separated the fedify init functionality from @fedify/cli into a standalone package to improve modularity and enable reuse by other tools such as @fedify/create. [#482 by Chanhaeng Lee]

  • Added runInit() function as the main initialization action handler.
  • Added initCommand and initOptions for CLI integration.
  • Added testInitCommand for comprehensive testing of all init combinations.

@fedify/create

• Created standalone project scaffolding CLI as the @fedify/create package. This enables creating new Fedify projects without installing the full @fedify/cli toolchain. [#351 by Chanhaeng Lee]

  • Supports npm init @fedify, pnpm create @fedify, yarn create @fedify, and bunx @fedify/create.
  • Uses @fedify/init internally for all initialization logic.
  • Supports the same interactive prompts and CLI options as fedify init.