$ forge changelog

Changelog

Every Forgekit release: new commands, SDK changes, fixes and the occasional breaking change, with upgrade steps.

v3.0.1

forge migrate handles monorepos

forge migrate finds every forge.json in a workspace, and two 3.0 regressions are fixed.

Thanks to everyone who upgraded in the first week and filed issues.

npm

npm install -D forgekit@3.0.1

bun

bun add -d forgekit@3.0.1

pnpm

pnpm add -D forgekit@3.0.1
  • forge migrate --workspace migrates every package in an npm, bun or pnpm workspace in one run
  • Fixed forge dev ignoring port from forge.config.ts
  • Fixed Okta group sync dropping groups with a / in the name
v3.0.0

Forgekit 3.0: one config file

forge.json is gone. Everything lives in forge.config.ts, and Node 18 support ends.

Breaking

  • forge.json is no longer read. Settings move to forge.config.ts
  • Node 18 is no longer supported. Forgekit needs Node 20.11 or later, or Bun 1.2
  • ctx.user.roles is now ctx.user.groups, to match how SSO providers name them

New

  • forge migrate rewrites forge.json into forge.config.ts and renames ctx.user.roles in your actions
  • defineConfig gives you autocomplete for every setting

Upgrade

Run the migration, then check the generated config:

npx forgekit@3 migrate
// forge.config.ts
import { defineConfig } from "forgekit";

export default defineConfig({
  name: "ops-tools",
  auth: { provider: "okta", groups: ["support", "finance"] },
});
v2.5.2

Two patch releases for the SDK

Fixes for action retries and date inputs across time zones.

Two small releases since v2.5.0. Upgrading to v2.5.2 picks up both.

v2.5.2

September 16, 2026

Fixed date inputs saving the previous day for users west of UTC.

forge logs now shows the action name instead of its internal id.

v2.5.1

September 9, 2026

Fixed actions retrying after a validation error. Only network errors and 5xx responses retry now.

defineAction accepts retries: 0 to turn retries off for one action.

v2.5.0

Typed actions in the SDK

defineAction infers input and output types from your schema, end to end.

defineAction takes a Zod or Valibot schema and infers the input type in the UI and the handler. No more hand-written types that drift.

npm

npm install @forgekit/sdk@2.5.0

bun

bun add @forgekit/sdk@2.5.0

pnpm

pnpm add @forgekit/sdk@2.5.0
import { defineAction } from "@forgekit/sdk";
import { z } from "zod";

export const refundOrder = defineAction({
  input: z.object({ orderId: z.string(), amountCents: z.number().int() }),
  async run({ input, db }) {
    return db.refunds.create({ data: input });
  },
});
  • Inputs are validated on the server before run is called
  • Validation errors show next to the matching form field
v2.4.1

Faster installs and Windows path fixes

The CLI is 40% smaller and forge init works on Windows paths with spaces.

  • The CLI package dropped from 18 MB to 11 MB, so npx forgekit starts faster on a cold cache
  • Fixed forge init failing on Windows when the project path contained a space
  • Fixed forge deploy printing the preview URL twice
  • forge --version now prints the SDK version next to the CLI version
v2.4.0

forge dev with hot reload

forge dev now reloads tools in place when you save, without losing form state.

forge dev watches your tool folder and reloads the changed module in the running preview. Form inputs, selected table rows and open drawers stay as they were.

forge dev ./tools/refunds --port 4310
  • Reloads in under 200 ms for most tools
  • Changes to forge.config.ts restart the dev server instead of hot reloading
  • --no-hmr turns it off if a tool keeps global state that doesn’t survive a reload