Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 12 additions & 19 deletions .github/workflows/release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,11 @@ name: Release

# Publishes all public packages to npm with provenance.
# Trigger: push a version tag (v0.1.0) or run manually from the Actions tab.
# Requires the NPM_TOKEN repo secret (npm automation token with publish
# rights on the @autter scope).
#
# Authenticates with npm trusted publishing (OIDC), not a stored token: each
# package's settings on npmjs.com trust this workflow (Autter-dev/autter-runtime,
# release.yml). A new public package needs its own trusted publisher before its
# first release from here, and renaming this file means recreating them all.

on:
push:
Expand All @@ -12,33 +15,25 @@ on:

permissions:
contents: read
id-token: write # npm provenance
id-token: write # npm trusted publishing and provenance

jobs:
publish:
# npm provenance currently accepts GitHub-hosted runners only.
# npm trusted publishing accepts GitHub-hosted runners only.
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: 22
registry-url: https://registry.npmjs.org
# npm answers a publish it refuses with E404, so name the account the
# token signs in as before building: an expired token, or one from an
# account without write access to @autter, fails here with a clear error.
- name: Check the npm token
run: |
user=$(npm whoami) || { echo "::error::NPM_TOKEN is invalid or expired (npm whoami failed)"; exit 1; }
echo "NPM_TOKEN signs in as npm user: $user"
if ! npm access list collaborators @autter/runtime-browser 2>/dev/null | grep -q "$user"; then
echo "::warning::npm user $user is not a collaborator on @autter/runtime-browser; publishes will fail with E404"
fi
env:
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
- run: npm install
- run: npm run build
- run: npm run size -w @autter/runtime-browser
# Trusted publishing needs npm 11.5.1 or newer; Node 22 ships npm 10.
- name: Update npm
run: |
npm install -g npm@11
npm --version
- name: Publish packages (skips versions that already exist)
run: |
# runtime-core is private (bundled into node + edge) and never published.
Expand All @@ -54,5 +49,3 @@ jobs:
npm publish -w "$name"
fi
done
env:
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
6 changes: 6 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,12 @@

## [Unreleased]

## [1.20.1] - 2026-11-15

Packages: `runtime-browser` 1.8.2, `runtime-node` 1.16.1, `runtime-edge` 1.4.3, `runtime-next` 1.11.1, `runtime-cli` 1.4.1, `otlp-ingester` 1.18.1. No code changes from 1.20.0.

- Releases are published to npm with trusted publishing instead of a stored npm token, so a publish can no longer fail because a token expired. Every package is republished once so npm records the new publisher for each.

## [1.20.0] - 2026-11-15

Packages: `runtime-node` 1.16.0, `runtime-next` 1.11.0 (now requires `runtime-node` 1.16.0 or later), `runtime-cli` 1.4.0, `otlp-ingester` 1.18.0, and the Python adapter (`adapters/python`, copied, not published). `runtime-core` (private, bundled into the others) changes too. `runtime-browser` and `runtime-edge` do not: their built `dist` is byte-identical to 1.19.0 (only `runtime-browser`'s README wording changed).
Expand Down
12 changes: 6 additions & 6 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,12 +36,12 @@ npm install @autter/runtime-edge # Cloudflare Workers, Vercel Edge, Deno, B

| Package | Version | Use it for |
| --- | --- | --- |
| `@autter/runtime-browser` | 1.8.1 | Browser errors + usage, coded-error duck typing, request-id capture |
| `@autter/runtime-node` | 1.16.0 | Node servers: OTel tracing, request summaries, coded errors, operations |
| `@autter/runtime-next` | 1.11.0 | Next.js: server + client + `/edge` for `middleware.ts` |
| `@autter/runtime-edge` | 1.4.2 | Fetch-only runtimes: request summaries and coded errors over `/v1/logs` |
| `@autter/otlp-ingester` | 1.18.0 | Self-hosted ingest — upgrade it **before** the SDKs |
| `@autter/runtime-cli` | 1.4.0 | Build time: debug ids + source map upload (CLI, Vite/Rollup, webpack, Next.js) |
| `@autter/runtime-browser` | 1.8.2 | Browser errors + usage, coded-error duck typing, request-id capture |
| `@autter/runtime-node` | 1.16.1 | Node servers: OTel tracing, request summaries, coded errors, operations |
| `@autter/runtime-next` | 1.11.1 | Next.js: server + client + `/edge` for `middleware.ts` |
| `@autter/runtime-edge` | 1.4.3 | Fetch-only runtimes: request summaries and coded errors over `/v1/logs` |
| `@autter/otlp-ingester` | 1.18.1 | Self-hosted ingest — upgrade it **before** the SDKs |
| `@autter/runtime-cli` | 1.4.1 | Build time: debug ids + source map upload (CLI, Vite/Rollup, webpack, Next.js) |

Minimum versions per feature, SDK and ingester are in one table:
[Version compatibility](docs/COMPATIBILITY.md#compatibility-table). Once
Expand Down
17 changes: 12 additions & 5 deletions docs/RELEASING.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,10 +4,16 @@

1. Create the **`autter` organization on npmjs.com** (Add Organization →
name `autter`) — this owns the `@autter` scope.
2. Generate an **automation token**: npmjs.com → Access Tokens →
Generate New Token → *Automation* (bypasses 2FA for CI).
3. Add it to this repo as the `NPM_TOKEN` secret:
`gh secret set NPM_TOKEN -R Autter-dev/autter-runtime`.
2. For **each public package** (`runtime-browser`, `runtime-node`,
`runtime-edge`, `runtime-next`, `runtime-cli`, `otlp-ingester`), add a
trusted publisher: npmjs.com → the package → Settings → Trusted Publisher
→ GitHub Actions, with organization `Autter-dev`, repository
`autter-runtime`, workflow `release.yml`, no environment, and
**Allow `npm publish`** ticked. A new trusted publisher must be used by a
publish within 2 days or npm drops it.
3. Once each package has published through it, set the package's
publishing access to *Require two-factor authentication and disallow
bypass 2fa tokens*. No npm token is stored in this repo.

## Publishing a release

Expand All @@ -21,7 +27,8 @@

The `Release` workflow builds everything, runs the browser size gate, and
publishes each package whose version doesn't already exist on the registry
— re-running is safe. Packages publish with npm **provenance**, so the
— re-running is safe. It authenticates with npm trusted publishing (OIDC), so
there is no token to renew. Packages publish with npm **provenance**, so the
version page shows it was built from this repo by CI.

Manual fallback: Actions tab → Release → Run workflow.
Expand Down
12 changes: 6 additions & 6 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion packages/otlp-ingester/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@autter/otlp-ingester",
"version": "1.18.0",
"version": "1.18.1",
"description": "Self-hostable OTLP + browser-error ingest service for Autter Runtime: normalises telemetry into a per-repo ClickHouse data model",
"license": "MIT",
"type": "module",
Expand Down
2 changes: 1 addition & 1 deletion packages/runtime-browser/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@autter/runtime-browser",
"version": "1.8.1",
"version": "1.8.2",
"description": "Tiny, dependency-free browser error and usage tracker for Autter Runtime (<10 KB gzipped)",
"license": "MIT",
"type": "module",
Expand Down
2 changes: 1 addition & 1 deletion packages/runtime-cli/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@autter/runtime-cli",
"version": "1.4.0",
"version": "1.4.1",
"description": "Readable stack traces for Autter Runtime: inject debug ids into JS bundles and upload their source maps (CLI, Vite/Rollup, webpack and Next.js plugins)",
"license": "MIT",
"type": "module",
Expand Down
2 changes: 1 addition & 1 deletion packages/runtime-edge/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@autter/runtime-edge",
"version": "1.4.2",
"version": "1.4.3",
"description": "Autter Runtime for edge runtimes (Cloudflare Workers, Vercel Edge, Deno, Bun): request wide events and coded errors over fetch, zero dependencies",
"license": "MIT",
"type": "module",
Expand Down
2 changes: 1 addition & 1 deletion packages/runtime-next/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@autter/runtime-next",
"version": "1.11.0",
"version": "1.11.1",
"description": "One-command Autter Runtime for Next.js: server OTel, request wide events, coded errors, browser tracker, relay route, edge middleware and React error boundary",
"license": "MIT",
"type": "module",
Expand Down
2 changes: 1 addition & 1 deletion packages/runtime-node/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@autter/runtime-node",
"version": "1.16.0",
"version": "1.16.1",
"description": "Autter Runtime for Node.js: request wide events, coded errors, operation logging, same-origin browser relay and a curated OpenTelemetry server tracker",
"license": "MIT",
"type": "module",
Expand Down
Loading