trigger.dev 4.0.0-v4-beta.28 → 4.0.0

package/README.md

@@ -1,10 +1,30 @@
+<div align="center">
+<picture>
+  <source media="(prefers-color-scheme: dark)" srcset="https://imagedelivery.net/3TbraffuDZ4aEf8KWOmI_w/a45d1fa2-0ae8-4a39-4409-f4f934bfae00/public">
+  <source media="(prefers-color-scheme: light)" srcset="https://imagedelivery.net/3TbraffuDZ4aEf8KWOmI_w/3f5ad4c1-c4c8-4277-b622-290e7f37bd00/public">
+  <img alt="Trigger.dev logo" src="https://imagedelivery.net/3TbraffuDZ4aEf8KWOmI_w/a45d1fa2-0ae8-4a39-4409-f4f934bfae00/public">
+</picture>
+
+[![npm version](https://img.shields.io/npm/v/trigger.dev.svg)](https://www.npmjs.com/package/trigger.dev)
+[![npm downloads](https://img.shields.io/npm/dm/trigger.dev.svg)](https://www.npmjs.com/package/trigger.dev)
+[![GitHub stars](https://img.shields.io/github/stars/triggerdotdev/trigger.dev?style=social)](https://github.com/triggerdotdev/trigger.dev)
+[![TypeScript](https://img.shields.io/badge/%3C%2F%3E-TypeScript-%230074c1.svg)](https://www.typescriptlang.org/)
+[![License: ](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+[![Open Source](https://img.shields.io/badge/Open%20Source-%E2%9D%A4-red)](https://github.com/triggerdotdev/trigger.dev)
+
+[Discord](https://trigger.dev/discord) | [Website](https://trigger.dev) | [Issues](https://github.com/triggerdotdev/trigger.dev/issues) | [Docs](https://trigger.dev/docs) | [Examples](https://trigger.dev/docs/examples)
+
+</div>
+
 # Trigger.dev CLI
 
 A CLI that allows you to create, run locally and deploy Trigger.dev background tasks.
 
 Note: this only works with Trigger.dev v3 projects and later. For older projects use the [@trigger.dev/cli](https://www.npmjs.com/package/@trigger.dev/cli) package.
 
-Trigger.dev is an open source platform that makes it easy to create event-driven background tasks directly in your existing project.
+## About Trigger.dev
+
+Trigger.dev is an open source platform for building and deploying fully-managed AI agents and workflows. Write workflows in normal async TypeScript for everything from simple tasks to long-running AI agents, heavy media processing, complex real-time systems and more. Complete with full observability, managed queues, and elastic infrastructure which handles the horizontal scaling.
 
 ## Commands
 
@@ -17,38 +37,14 @@ Trigger.dev is an open source platform that makes it easy to create event-driven
 | [whoami](https://trigger.dev/docs/cli-whoami-commands)               | Display the current logged in user and project details.            |
 | [logout](https://trigger.dev/docs/cli-logout-commands)               | Logout of Trigger.dev.                                             |
 | [list-profiles](https://trigger.dev/docs/cli-list-profiles-commands) | List all of your CLI profiles.                                     |
+| [preview archive](https://trigger.dev/docs/cli-preview-archive)      | Archive a preview branch.                                          |
+| [promote](https://trigger.dev/docs/cli-promote-commands)             | Promote a previously deployed version to the current version.      |
+| [switch](https://trigger.dev/docs/cli-switch)                        | Switch between CLI profiles.                                       |
 | [update](https://trigger.dev/docs/cli-update-commands)               | Updates all `@trigger.dev/*` packages to match the CLI version.    |
 
-## MCP Server
-
-The [Model Context Protocol (MCP)](https://modelcontextprotocol.io/introduction) is an open protocol that allows you to provide custom tools
-to agentic LLM clients, like [Claude for Desktop](https://docs.anthropic.com/en/docs/claude-for-desktop/overview), [Cursor](https://www.cursor.com/), [Windsurf](https://windsurf.com/), etc...
-
-The Trigger.dev CLI can expose an MCP server and enable you interact with Trigger.dev in agentic LLM workflows. For example, you can use
-it to trigger tasks via natural language, view task runs, view logs, debug issues with task runs, etc...
-
-### Starting the Trigger.dev MCP Server
-
-To start the Trigger.dev MCP server, simply pass the `--mcp` flag to the `dev` command:
-
-```bash
-trigger dev --mcp
-```
-
-By default it runs on port `3333`. You can change this by passing the `--mcp-port` flag:
-
-```bash
-trigger dev --mcp --mcp-port 3334
-```
-
-### Configuring your MCP client
-
-This depends on what tool you are using. For Cursor, the configuration is in the [.cursor/mcp.json](../../.cursor/mcp.json) file
-and should be good to go as long as you use the default MCP server port.
-
-Check out [Cursor's docs](https://docs.cursor.com/context/model-context-protocol) for further details.
+## CLI documentation
 
-Tip: try out [Cursor's YOLO mode](https://docs.cursor.com/context/model-context-protocol#yolo-mode) for a seamless experience :D
+For more information on the CLI, please refer to our [docs](https://trigger.dev/docs/cli-introduction).
 
 ## Support
 

package/dist/esm/version.js

@@ -1,2 +1,2 @@
-export const VERSION = "4.0.0-v4-beta.28";
+export const VERSION = "4.0.0";
 //# sourceMappingURL=version.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "trigger.dev",
-  "version": "4.0.0-v4-beta.28",
+  "version": "4.0.0",
   "description": "A Command-Line Interface for Trigger.dev (v3) projects",
   "type": "module",
   "license": "MIT",
@@ -80,9 +80,9 @@
     "@opentelemetry/resources": "2.0.1",
     "@opentelemetry/sdk-trace-node": "2.0.1",
     "@opentelemetry/semantic-conventions": "1.36.0",
-    "@trigger.dev/build": "4.0.0-v4-beta.28",
-    "@trigger.dev/core": "4.0.0-v4-beta.28",
-    "@trigger.dev/schema-to-json": "4.0.0-v4-beta.28",
+    "@trigger.dev/build": "4.0.0",
+    "@trigger.dev/core": "4.0.0",
+    "@trigger.dev/schema-to-json": "4.0.0",
     "ansi-escapes": "^7.0.0",
     "braces": "^3.0.3",
     "c12": "^1.11.1",