[ai] Publish @workflow/ai 5.x as 5.0.1 - #4548
Merged
Merged
Conversation
@workflow/ai@5.0.0 was already taken on npm by an older build, so changeset publish skipped it and check-published fails on every main release run. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
🦋 Changeset detectedLatest commit: adf68b9 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
Contributor
Sim WorldSimulated world deterministic testing for races. Traces 🟠 world-sim scenario book — 1 fail of 42 total
Full trace: |
VaguelySerious
marked this pull request as ready for review
October 1, 2026 01:59
karthikscale3
approved these changes
Oct 1, 2026
karthikscale3
left a comment
Contributor
There was a problem hiding this comment.
Reviewed the changeset and release flow. This correctly bumps @workflow/ai to an unused 5.0.1 so the current 5.x build can publish and move the latest npm tag. No blocking findings.
Contributor
|
No backport to This commit adds only a changeset file, which is release plumbing and explicitly excluded from backports. It is also specific to the 5.x publish problem on To override, re-run the Backport to stable workflow manually via |
This was referenced Oct 1, 2026
Merged
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
@workflow/ai@5.0.0already exists on npm: it was published on 2026-06-02 from an older build, and it peers onworkflow ^4.3.0. When the GA release set the package to5.0.0,changeset publishskipped it because that version was already taken. So the 5.x code was never published, andlateststill points to4.2.1, which requiresworkflow ^4.8.5.Because of this, every
Releaserun onmainfails at "Verify every package version on this commit is on npm":This adds a patch changeset so the next release publishes
@workflow/ai@5.0.1and moveslatestto it.After it ships, someone with publish rights should deprecate the stale build so anyone pinned to exactly
5.0.0gets a warning:🤖 Generated with Claude Code