# triggerdotdev/trigger.dev · RepoSense Release & Migration Intelligence

> CLI and MCP logins are now bound to the machine that start. Drop-in upgrade. Migration: None.

## Metadata
- **Repository URL**: https://github.com/triggerdotdev/trigger.dev
- **Primary Package**: `@trigger.dev/sdk` (NPM)
- **Categories**: `AI-AGENT`, `AI-FRAMEWORK`, `BACKEND`
- **Latest Version**: `v4.8.3`
- **Semantic Status**: `COMPATIBLE`
- **Bundle Size Impact (unavailable)**: `Size Unavailable`
- **Atom Ingestion Feed**: https://github.com/triggerdotdev/trigger.dev/releases.atom

## The Human Context (Plain-English Pitch)
@trigger.dev/sdk is an open-source library and developer tool in the triggerdotdev/trigger.dev ecosystem. It saves developers from writing repetitive low-level boilerplate from scratch by providing a battle-tested, open-source implementation ready for production.

## Stage 1 Executive Summary ([Core Change] + [Required Action] + [Migration Effort])
CLI and MCP logins are now bound to the machine that start. Drop-in upgrade. Migration: None.

## Breaking Changes & Required Actions
- CLI and MCP logins are now bound to the machine that started them. Approving a login in your browser sends you back to the CLI automatically, or, when the browser is on another ...
- Add `trigger webhooks set-secret` and `trigger webhooks generate-secret`, which store a webhook endpoint's signing secret without printing it. `set-secret` reads the secret from...
- Deprecates the legacy Bun runtime. `runtime: "bun"` (and its explicit spelling `"bun-legacy"`), which deploys Bun 1.3.3 with Node.js 20 alongside it, now prints a deprecation wa...
- Add `trigger.refresh(ctx, id)` to request an earlier status check for a Convex-tracked run, so applications using Trigger Realtime can publish results without waiting for the ne...

## Migration Snippet
```ts
npm install @trigger.dev/sdk@4.8.3
```

## Ecosystem Compatibility Matrix & Graph Warnings
- **TypeScript 5.x** [`COMPATIBLE`]: Ships standard TypeScript declaration files without type regressions.

## Zero-Noise Release Timeline
- **v4.8.3** (2026-10-30) [COMPATIBLE]: CLI and MCP logins are now bound to the machine that start. Drop-in upgrade. Migration: None.

## Upgrade & Migration Q&A (GEO Direct Answers)
### Is triggerdotdev/trigger.dev v4.8.3 safe to upgrade in production?
triggerdotdev/trigger.dev v4.8.3 is classified as COMPATIBLE (PATCH release). CLI and MCP logins are now bound to the machine that start. Drop-in upgrade. Migration: None.

### What breaking changes or compatibility risks exist in triggerdotdev/trigger.dev v4.8.3?
No breaking API changes or peer dependency conflicts are recorded for triggerdotdev/trigger.dev v4.8.3 in the RepoSense compatibility graph.

### What is the bundle size impact of @trigger.dev/sdk v4.8.3?
Measured bundle size telemetry is currently unavailable for @trigger.dev/sdk v4.8.3; verify build output locally before deploying.

### How do I upgrade @trigger.dev/sdk to v4.8.3?
Upgrade @trigger.dev/sdk to v4.8.3 by running "npm install @trigger.dev/sdk@4.8.3" and applying the migration steps: npm install @trigger.dev/sdk@4.8.3