mirror of
https://github.com/vercel/workflow.git
synced 2026-09-14 19:59:43 +08:00
80ccca023d
@workflow/ai was accidentally published to `latest` as 5.0.0, 6.0.0, and 7.0.0. Root cause: it peer-depends on `workflow`, and changesets' `onlyUpdatePeerDependentsWhenOutOfRange` defaults to false, so every `workflow` minor on `stable` force-bumped ai a full major despite no breaking changes. - Add `onlyUpdatePeerDependentsWhenOutOfRange: true` so ai only majors when a new `workflow` version actually leaves its `^4` peer range. - Reset packages/ai/package.json from 7.0.0 back to 4.1.2; a patch changeset re-releases it as 4.1.3 on the 4.x line (carries the inline-sourcemaps packaging change that was trapped in 6.0.0). Verified via `changeset status`: with pending `workflow` minors, @workflow/ai now bumps patch, not major. Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
38 lines
761 B
JSON
38 lines
761 B
JSON
{
|
|
"$schema": "https://unpkg.com/@changesets/config@3.1.1/schema.json",
|
|
"changelog": [
|
|
"./changelog.mjs",
|
|
{
|
|
"repo": "vercel/workflow"
|
|
}
|
|
],
|
|
"commit": false,
|
|
"fixed": [
|
|
[
|
|
"workflow",
|
|
"@workflow/core"
|
|
],
|
|
[
|
|
"@workflow/web",
|
|
"@workflow/web-shared"
|
|
]
|
|
],
|
|
"linked": [],
|
|
"access": "public",
|
|
"baseBranch": "stable",
|
|
"updateInternalDependencies": "patch",
|
|
"___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH": {
|
|
"onlyUpdatePeerDependentsWhenOutOfRange": true
|
|
},
|
|
"ignore": [
|
|
"docs",
|
|
"tarballs",
|
|
"nextjs-turbopack",
|
|
"nextjs-webpack",
|
|
"workflow-sdk-compiler-playground",
|
|
"@workflow/docs-typecheck",
|
|
"@workflow/example-*",
|
|
"@workflow/vitest-workbench"
|
|
]
|
|
}
|