github-featured/triggerdotdev--trigger.dev
2
0
Fork 0
Code Issues Pull Requests Deployments Models Agent Notes Packages Projects Releases Wiki Activity

chore: Update version for release (#1504)

Browse Source 
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
This commit is contained in:
github-actions[bot]
2024-11-28 15:26:11 +00:00
committed by GitHub
parent 1077709e15
commit 6bf3bbcfd7
15 changed files with 360 additions and 125 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.changeset/perfect-onions-call.md
-80
View File
@@ -1,80 +0,0 @@
---
"@trigger.dev/sdk": patch
"trigger.dev": patch
"@trigger.dev/core": patch
---
Added new batch.trigger and batch.triggerByTask methods that allows triggering multiple different tasks in a single batch:
```ts
import { batch } from '@trigger.dev/sdk/v3';
import type { myTask1, myTask2 } from './trigger/tasks';
// Somewhere in your backend code
const response = await batch.trigger<typeof myTask1 | typeof myTask2>([
{ id: 'task1', payload: { foo: 'bar' } },
{ id: 'task2', payload: { baz: 'qux' } },
]);
for (const run of response.runs) {
if (run.ok) {
console.log(run.output);
} else {
console.error(run.error);
}
}
```
Or if you are inside of a task, you can use `triggerByTask`:
```ts
import { batch, task, runs } from '@trigger.dev/sdk/v3';
export const myParentTask = task({
id: 'myParentTask',
run: async () => {
const response = await batch.triggerByTask([
{ task: myTask1, payload: { foo: 'bar' } },
{ task: myTask2, payload: { baz: 'qux' } },
]);
const run1 = await runs.retrieve(response.runs[0]);
console.log(run1.output) // typed as { foo: string }
const run2 = await runs.retrieve(response.runs[1]);
console.log(run2.output) // typed as { baz: string }
const response2 = await batch.triggerByTaskAndWait([
{ task: myTask1, payload: { foo: 'bar' } },
{ task: myTask2, payload: { baz: 'qux' } },
]);
if (response2.runs[0].ok) {
console.log(response2.runs[0].output) // typed as { foo: string }
}
if (response2.runs[1].ok) {
console.log(response2.runs[1].output) // typed as { baz: string }
}
}
});
export const myTask1 = task({
id: 'myTask1',
run: async () => {
return {
foo: 'bar'
}
}
});
export const myTask2 = task({
id: 'myTask2',
run: async () => {
return {
baz: 'qux'
}
}
});
```
.changeset/ten-pans-itch.md
-25
View File
@@ -1,25 +0,0 @@
---
"@trigger.dev/react-hooks": minor
"@trigger.dev/sdk": minor
"@trigger.dev/core": minor
---
Improved Batch Triggering:
- The new Batch Trigger endpoint is now asynchronous and supports up to 500 runs per request.
- The new endpoint also supports triggering multiple different tasks in a single batch request (support in the SDK coming soon).
- The existing `batchTrigger` method now supports the new endpoint, and shouldn't require any changes to your code.
- Idempotency keys now expire after 24 hours, and you can customize the expiration time when creating a new key by using the `idempotencyKeyTTL` parameter:
```ts
await myTask.batchTrigger([{ payload: { foo: "bar" }}], { idempotencyKey: "my-key", idempotencyKeyTTL: "60s" })
// Works for individual items as well:
await myTask.batchTrigger([{ payload: { foo: "bar" }, options: { idempotencyKey: "my-key", idempotencyKeyTTL: "60s" }}])
// And `trigger`:
await myTask.trigger({ foo: "bar" }, { idempotencyKey: "my-key", idempotencyKeyTTL: "60s" });
```
### Breaking Changes
- We've removed the `idempotencyKey` option from `triggerAndWait` and `batchTriggerAndWait`, because it can lead to permanently frozen runs in deployed tasks. We're working on upgrading our entire system to support idempotency keys on these methods, and we'll re-add the option once that's complete.
.changeset/wild-needles-hunt.md
-7
View File
@@ -1,7 +0,0 @@
---
"@trigger.dev/react-hooks": patch
"@trigger.dev/sdk": patch
"@trigger.dev/core": patch
---
Added ability to subscribe to a batch of runs using runs.subscribeToBatch
packages/build/CHANGELOG.md
+7
View File
@@ -1,5 +1,12 @@
# @trigger.dev/build
## 3.3.0
### Patch Changes
- Updated dependencies:
- `@trigger.dev/core@3.3.0`
## 3.2.2
### Patch Changes
packages/build/package.json
+2 -2
View File
@@ -1,6 +1,6 @@
{
"name": "@trigger.dev/build",
"version": "3.2.2",
"version": "3.3.0",
"description": "trigger.dev build extensions",
"license": "MIT",
"publishConfig": {
@@ -65,7 +65,7 @@
"check-exports": "attw --pack ."
},
"dependencies": {
"@trigger.dev/core": "workspace:3.2.2",
"@trigger.dev/core": "workspace:3.3.0",
"pkg-types": "^1.1.3",
"tinyglobby": "^0.2.2",
"tsconfck": "3.1.3"
packages/cli-v3/CHANGELOG.md
+82
View File
@@ -1,5 +1,87 @@
# trigger.dev
## 3.3.0
### Patch Changes
- Added new batch.trigger and batch.triggerByTask methods that allows triggering multiple different tasks in a single batch: ([#1502](https://github.com/triggerdotdev/trigger.dev/pull/1502))
```ts
import { batch } from "@trigger.dev/sdk/v3";
import type { myTask1, myTask2 } from "./trigger/tasks";
// Somewhere in your backend code
const response = await batch.trigger<typeof myTask1 | typeof myTask2>([
{ id: "task1", payload: { foo: "bar" } },
{ id: "task2", payload: { baz: "qux" } },
]);
for (const run of response.runs) {
if (run.ok) {
console.log(run.output);
} else {
console.error(run.error);
}
}
```
Or if you are inside of a task, you can use `triggerByTask`:
```ts
import { batch, task, runs } from "@trigger.dev/sdk/v3";
export const myParentTask = task({
id: "myParentTask",
run: async () => {
const response = await batch.triggerByTask([
{ task: myTask1, payload: { foo: "bar" } },
{ task: myTask2, payload: { baz: "qux" } },
]);
const run1 = await runs.retrieve(response.runs[0]);
console.log(run1.output); // typed as { foo: string }
const run2 = await runs.retrieve(response.runs[1]);
console.log(run2.output); // typed as { baz: string }
const response2 = await batch.triggerByTaskAndWait([
{ task: myTask1, payload: { foo: "bar" } },
{ task: myTask2, payload: { baz: "qux" } },
]);
if (response2.runs[0].ok) {
console.log(response2.runs[0].output); // typed as { foo: string }
}
if (response2.runs[1].ok) {
console.log(response2.runs[1].output); // typed as { baz: string }
}
},
});
export const myTask1 = task({
id: "myTask1",
run: async () => {
return {
foo: "bar",
};
},
});
export const myTask2 = task({
id: "myTask2",
run: async () => {
return {
baz: "qux",
};
},
});
```
- Updated dependencies:
- `@trigger.dev/core@3.3.0`
- `@trigger.dev/build@3.3.0`
## 3.2.2
### Patch Changes
packages/cli-v3/package.json
+3 -3
View File
@@ -1,6 +1,6 @@
{
"name": "trigger.dev",
"version": "3.2.2",
"version": "3.3.0",
"description": "A Command-Line Interface for Trigger.dev (v3) projects",
"type": "module",
"license": "MIT",
@@ -87,8 +87,8 @@
"@opentelemetry/sdk-trace-base": "1.25.1",
"@opentelemetry/sdk-trace-node": "1.25.1",
"@opentelemetry/semantic-conventions": "1.25.1",
"@trigger.dev/build": "workspace:3.2.2",
"@trigger.dev/core": "workspace:3.2.2",
"@trigger.dev/build": "workspace:3.3.0",
"@trigger.dev/core": "workspace:3.3.0",
"c12": "^1.11.1",
"chalk": "^5.2.0",
"cli-table3": "^0.6.3",
packages/core/CHANGELOG.md
+107
View File
@@ -1,5 +1,112 @@
# internal-platform
## 3.3.0
### Minor Changes
- Improved Batch Triggering: ([#1502](https://github.com/triggerdotdev/trigger.dev/pull/1502))
- The new Batch Trigger endpoint is now asynchronous and supports up to 500 runs per request.
- The new endpoint also supports triggering multiple different tasks in a single batch request (support in the SDK coming soon).
- The existing `batchTrigger` method now supports the new endpoint, and shouldn't require any changes to your code.
- Idempotency keys now expire after 24 hours, and you can customize the expiration time when creating a new key by using the `idempotencyKeyTTL` parameter:
```ts
await myTask.batchTrigger([{ payload: { foo: "bar" } }], {
idempotencyKey: "my-key",
idempotencyKeyTTL: "60s",
});
// Works for individual items as well:
await myTask.batchTrigger([
{ payload: { foo: "bar" }, options: { idempotencyKey: "my-key", idempotencyKeyTTL: "60s" } },
]);
// And `trigger`:
await myTask.trigger({ foo: "bar" }, { idempotencyKey: "my-key", idempotencyKeyTTL: "60s" });
```
### Breaking Changes
- We've removed the `idempotencyKey` option from `triggerAndWait` and `batchTriggerAndWait`, because it can lead to permanently frozen runs in deployed tasks. We're working on upgrading our entire system to support idempotency keys on these methods, and we'll re-add the option once that's complete.
### Patch Changes
- Added new batch.trigger and batch.triggerByTask methods that allows triggering multiple different tasks in a single batch: ([#1502](https://github.com/triggerdotdev/trigger.dev/pull/1502))
```ts
import { batch } from "@trigger.dev/sdk/v3";
import type { myTask1, myTask2 } from "./trigger/tasks";
// Somewhere in your backend code
const response = await batch.trigger<typeof myTask1 | typeof myTask2>([
{ id: "task1", payload: { foo: "bar" } },
{ id: "task2", payload: { baz: "qux" } },
]);
for (const run of response.runs) {
if (run.ok) {
console.log(run.output);
} else {
console.error(run.error);
}
}
```
Or if you are inside of a task, you can use `triggerByTask`:
```ts
import { batch, task, runs } from "@trigger.dev/sdk/v3";
export const myParentTask = task({
id: "myParentTask",
run: async () => {
const response = await batch.triggerByTask([
{ task: myTask1, payload: { foo: "bar" } },
{ task: myTask2, payload: { baz: "qux" } },
]);
const run1 = await runs.retrieve(response.runs[0]);
console.log(run1.output); // typed as { foo: string }
const run2 = await runs.retrieve(response.runs[1]);
console.log(run2.output); // typed as { baz: string }
const response2 = await batch.triggerByTaskAndWait([
{ task: myTask1, payload: { foo: "bar" } },
{ task: myTask2, payload: { baz: "qux" } },
]);
if (response2.runs[0].ok) {
console.log(response2.runs[0].output); // typed as { foo: string }
}
if (response2.runs[1].ok) {
console.log(response2.runs[1].output); // typed as { baz: string }
}
},
});
export const myTask1 = task({
id: "myTask1",
run: async () => {
return {
foo: "bar",
};
},
});
export const myTask2 = task({
id: "myTask2",
run: async () => {
return {
baz: "qux",
};
},
});
```
- Added ability to subscribe to a batch of runs using runs.subscribeToBatch ([#1502](https://github.com/triggerdotdev/trigger.dev/pull/1502))
## 3.2.2
## 3.2.1
packages/core/package.json
+1 -1
View File
@@ -1,6 +1,6 @@
{
"name": "@trigger.dev/core",
"version": "3.2.2",
"version": "3.3.0",
"description": "Core code used across the Trigger.dev SDK and platform",
"license": "MIT",
"publishConfig": {
packages/react-hooks/CHANGELOG.md
+35
View File
@@ -1,5 +1,40 @@
# @trigger.dev/react-hooks
## 3.3.0
### Minor Changes
- Improved Batch Triggering: ([#1502](https://github.com/triggerdotdev/trigger.dev/pull/1502))
- The new Batch Trigger endpoint is now asynchronous and supports up to 500 runs per request.
- The new endpoint also supports triggering multiple different tasks in a single batch request (support in the SDK coming soon).
- The existing `batchTrigger` method now supports the new endpoint, and shouldn't require any changes to your code.
- Idempotency keys now expire after 24 hours, and you can customize the expiration time when creating a new key by using the `idempotencyKeyTTL` parameter:
```ts
await myTask.batchTrigger([{ payload: { foo: "bar" } }], {
idempotencyKey: "my-key",
idempotencyKeyTTL: "60s",
});
// Works for individual items as well:
await myTask.batchTrigger([
{ payload: { foo: "bar" }, options: { idempotencyKey: "my-key", idempotencyKeyTTL: "60s" } },
]);
// And `trigger`:
await myTask.trigger({ foo: "bar" }, { idempotencyKey: "my-key", idempotencyKeyTTL: "60s" });
```
### Breaking Changes
- We've removed the `idempotencyKey` option from `triggerAndWait` and `batchTriggerAndWait`, because it can lead to permanently frozen runs in deployed tasks. We're working on upgrading our entire system to support idempotency keys on these methods, and we'll re-add the option once that's complete.
### Patch Changes
- Added ability to subscribe to a batch of runs using runs.subscribeToBatch ([#1502](https://github.com/triggerdotdev/trigger.dev/pull/1502))
- Updated dependencies:
- `@trigger.dev/core@3.3.0`
## 3.2.2
### Patch Changes
packages/react-hooks/package.json
+2 -2
View File
@@ -1,6 +1,6 @@
{
"name": "@trigger.dev/react-hooks",
"version": "3.2.2",
"version": "3.3.0",
"description": "trigger.dev react hooks",
"license": "MIT",
"publishConfig": {
@@ -37,7 +37,7 @@
"check-exports": "attw --pack ."
},
"dependencies": {
"@trigger.dev/core": "workspace:^3.2.2",
"@trigger.dev/core": "workspace:^3.3.0",
"swr": "^2.2.5"
},
"devDependencies": {
packages/rsc/CHANGELOG.md
+7
View File
@@ -1,5 +1,12 @@
# @trigger.dev/rsc
## 3.3.0
### Patch Changes
- Updated dependencies:
- `@trigger.dev/core@3.3.0`
## 3.2.2
### Patch Changes
packages/rsc/package.json
+3 -3
View File
@@ -1,6 +1,6 @@
{
"name": "@trigger.dev/rsc",
"version": "3.2.2",
"version": "3.3.0",
"description": "trigger.dev rsc",
"license": "MIT",
"publishConfig": {
@@ -37,14 +37,14 @@
"check-exports": "attw --pack ."
},
"dependencies": {
"@trigger.dev/core": "workspace:^3.2.2",
"@trigger.dev/core": "workspace:^3.3.0",
"mlly": "^1.7.1",
"react": "19.0.0-rc.1",
"react-dom": "19.0.0-rc.1"
},
"devDependencies": {
"@arethetypeswrong/cli": "^0.15.4",
"@trigger.dev/build": "workspace:^3.2.2",
"@trigger.dev/build": "workspace:^3.3.0",
"@types/node": "^20.14.14",
"@types/react": "*",
"@types/react-dom": "*",
packages/trigger-sdk/CHANGELOG.md
+109
View File
@@ -1,5 +1,114 @@
# @trigger.dev/sdk
## 3.3.0
### Minor Changes
- Improved Batch Triggering: ([#1502](https://github.com/triggerdotdev/trigger.dev/pull/1502))
- The new Batch Trigger endpoint is now asynchronous and supports up to 500 runs per request.
- The new endpoint also supports triggering multiple different tasks in a single batch request (support in the SDK coming soon).
- The existing `batchTrigger` method now supports the new endpoint, and shouldn't require any changes to your code.
- Idempotency keys now expire after 24 hours, and you can customize the expiration time when creating a new key by using the `idempotencyKeyTTL` parameter:
```ts
await myTask.batchTrigger([{ payload: { foo: "bar" } }], {
idempotencyKey: "my-key",
idempotencyKeyTTL: "60s",
});
// Works for individual items as well:
await myTask.batchTrigger([
{ payload: { foo: "bar" }, options: { idempotencyKey: "my-key", idempotencyKeyTTL: "60s" } },
]);
// And `trigger`:
await myTask.trigger({ foo: "bar" }, { idempotencyKey: "my-key", idempotencyKeyTTL: "60s" });
```
### Breaking Changes
- We've removed the `idempotencyKey` option from `triggerAndWait` and `batchTriggerAndWait`, because it can lead to permanently frozen runs in deployed tasks. We're working on upgrading our entire system to support idempotency keys on these methods, and we'll re-add the option once that's complete.
### Patch Changes
- Added new batch.trigger and batch.triggerByTask methods that allows triggering multiple different tasks in a single batch: ([#1502](https://github.com/triggerdotdev/trigger.dev/pull/1502))
```ts
import { batch } from "@trigger.dev/sdk/v3";
import type { myTask1, myTask2 } from "./trigger/tasks";
// Somewhere in your backend code
const response = await batch.trigger<typeof myTask1 | typeof myTask2>([
{ id: "task1", payload: { foo: "bar" } },
{ id: "task2", payload: { baz: "qux" } },
]);
for (const run of response.runs) {
if (run.ok) {
console.log(run.output);
} else {
console.error(run.error);
}
}
```
Or if you are inside of a task, you can use `triggerByTask`:
```ts
import { batch, task, runs } from "@trigger.dev/sdk/v3";
export const myParentTask = task({
id: "myParentTask",
run: async () => {
const response = await batch.triggerByTask([
{ task: myTask1, payload: { foo: "bar" } },
{ task: myTask2, payload: { baz: "qux" } },
]);
const run1 = await runs.retrieve(response.runs[0]);
console.log(run1.output); // typed as { foo: string }
const run2 = await runs.retrieve(response.runs[1]);
console.log(run2.output); // typed as { baz: string }
const response2 = await batch.triggerByTaskAndWait([
{ task: myTask1, payload: { foo: "bar" } },
{ task: myTask2, payload: { baz: "qux" } },
]);
if (response2.runs[0].ok) {
console.log(response2.runs[0].output); // typed as { foo: string }
}
if (response2.runs[1].ok) {
console.log(response2.runs[1].output); // typed as { baz: string }
}
},
});
export const myTask1 = task({
id: "myTask1",
run: async () => {
return {
foo: "bar",
};
},
});
export const myTask2 = task({
id: "myTask2",
run: async () => {
return {
baz: "qux",
};
},
});
```
- Added ability to subscribe to a batch of runs using runs.subscribeToBatch ([#1502](https://github.com/triggerdotdev/trigger.dev/pull/1502))
- Updated dependencies:
- `@trigger.dev/core@3.3.0`
## 3.2.2
### Patch Changes
packages/trigger-sdk/package.json
+2 -2
View File
@@ -1,6 +1,6 @@
{
"name": "@trigger.dev/sdk",
"version": "3.2.2",
"version": "3.3.0",
"description": "trigger.dev Node.JS SDK",
"license": "MIT",
"publishConfig": {
@@ -48,7 +48,7 @@
"@opentelemetry/api": "1.9.0",
"@opentelemetry/api-logs": "0.52.1",
"@opentelemetry/semantic-conventions": "1.25.1",
"@trigger.dev/core": "workspace:3.2.2",
"@trigger.dev/core": "workspace:3.3.0",
"chalk": "^5.2.0",
"cronstrue": "^2.21.0",
"debug": "^4.3.4",