Skip to content
Back to skills

V1.2.0

BSecurity

Upgrade a project to forge v1.2.0. In mock mode every RPC of every service a frontend has generated TypeScript for — custom reads, streams, vendored contracts — now answers a deterministic, schema-valid default instead of Unimplemented; forge generate writes src/mocks/services/<service>_gen.ts per service and mock-transport_gen.ts gathers them. Hand-written scenario handlers that only filled in a response shape can become mockService(Service, { rpc: (req, d) => patch(d.rpc(req), …) }) overrid...

  • 10 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added November 13, 2026
developmenttypescriptgobashsqlnextjsgitfrontendbackend

Security analysis

B80/100
  • criticalSends environment variables or credentials to an external URL
  • mediumInstalls packages at runtime which could introduce malicious dependencies

Pro shows the line behind each finding and how to fix it

Scanned November 13, 2026

npx -y skills add reliant-labs/forge --skill v1.2.0 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of V1.2.0?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for V1.2.0
[![Security: B — Skills Directory](https://www.skillsdirectory.com/api/skills/reliant-labs-v1-2-0/badge)](https://www.skillsdirectory.com/skills/reliant-labs-v1-2-0)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: v1.2.0
description: Upgrade a project to forge v1.2.0. In mock mode every RPC of every service a frontend has generated TypeScript for — custom reads, streams, vendored contracts — now answers a deterministic, schema-valid default instead of Unimplemented; forge generate writes src/mocks/services/<service>_gen.ts per service and mock-transport_gen.ts gathers them. Hand-written scenario handlers that only filled in a response shape can become mockService(Service, { rpc: (req, d) => patch(d.rpc(req), …) }) overrides, typed for vendored services too. Use when a browser frontend has src/lib/mock-transport_gen.ts. Also: forge/pkg/approval, added in v1.0.16, is deprecated (out of scope) and will be removed in the next major; nothing in forge, reliant or control-plane imported it. Use when a Go file imports forge/pkg/approval.
version: v1.2.0
detection: for f in frontends/*/src/lib/mock-transport_gen.ts; do [ -f "$f" ] && exit 0; done; grep -rqs --include='*.go' 'forge/pkg/approval"' . && exit 0; exit 1
---

# Upgrading to v1.2.0

## 1. Every RPC answers in mock mode

**Use when** a Next.js or Vite frontend has `src/lib/mock-transport_gen.ts`.

### What changed

`forge generate` writes one Tier-1 module per Connect service found in the
frontend's `src/gen/**/*_pb.ts` — the project's own protos and any vendored
contract another buf template generated there:

```
src/mocks/services/<service>_gen.ts   export const <service>Defaults = serviceDefaults(<Service>);
```

`src/lib/mock-transport_gen.ts` gathers them and passes them to the engine as
`services`. The dispatch order gains one rung, after the entity fixtures:
scenario handler → hybrid passthrough → fixtures → **service defaults** →
`Unimplemented`. A default is built at runtime from the service's descriptor
(field names, enums, maps, oneofs, well-known types, protovalidate rules) and is
the same for the same request; the `frontend/mock-mode` skill lists what each
field becomes.

The new modules import `serviceDefaults` and `isServiceDefaults` from
`@reliantlabs/forge-web-runtime/mock-transport`; `forge generate` raises the
frontend's `@reliantlabs/forge-web-runtime` range to the release that has them.
Run `npm install` in the frontend after generating.

### What to check

- A mocked page that showed an error for a custom RPC now shows sample data.
  A test or a scenario that ASSERTED `Unimplemented` for an unmocked RPC must
  name that RPC now (a scenario handler that throws
  `new ConnectError("…", Code.Unimplemented)`).
- In hybrid mode (`passthrough: true`), unmatched RPCs still go to the backend:
  defaults rank below passthrough.

### Optional: shrink hand-written handlers

A scenario handler that built a whole response by hand to make a page render
can start from the default and change only what the scenario is about:

```ts
import { mockService, patch } from "@reliantlabs/forge-web-runtime/mock-transport";

handlers: {
  ...mockService(ReportService, {
    listReports: (req, d) => patch(d.listReports(req), { reports: [] }),
  }),
},
```

`mockService` is typed by the service descriptor, so a vendored service's
handlers no longer need the untyped `"pkg.v1.Svc/Method"` escape hatch.

## 2. `forge/pkg/approval` is deprecated

**Use when** a Go file imports `github.com/reliant-labs/forge/pkg/approval`.

### What changed

`pkg/approval` (`Propose`, `Decide`, `ExpireDue`, `Cancel`, `Redrive`,
`SchemaSQL`), added in v1.0.16 by #1753, is deprecated. It is outside forge's
scope: a pending-approval state machine is application logic, not framework.
Nothing in forge, its templates, reliant or control-plane imported it. It keeps
working unchanged throughout v1 (no further fixes or features), and the next
major removes it; staticcheck now flags each import (SA1019).

### What to do

Nothing is required in v1. To stop depending on it, copy the package from
v1.1.0 into your own module (for example
`internal/approval/`) and change the import path:

```bash
go mod download github.com/reliant-labs/forge@v1.1.0
cp -r "$(go env GOMODCACHE)/github.com/reliant-labs/forge@v1.1.0/pkg/approval" internal/approval
chmod -R u+w internal/approval   # the module cache is read-only
grep -rl --include='*.go' 'forge/pkg/approval"' . | xargs sed -i 's#github.com/reliant-labs/forge/pkg/approval"#<your-module>/internal/approval"#'
```

The `approvals` table your migration created from `approval.SchemaSQL` is
yours already; nothing about it changes.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in development →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.