Uh oh!
There was an error while loading. Please reload this page.
Version Packages (beta) - #3
Conversation
The latest updates on your projects. Learn more about Vercel for GitHub.
|
5ff1ad6 to
91cef71Compare91cef71 to
880dbe8CompareUh oh!
There was an error while loading. Please reload this page.
880dbe8 to
12f9c88Compare12f9c88 to
aa6aa5fCompare7fe6538 to
96f57baCompare| - Updated dependencies [731adff] | ||
| - Updated dependencies [57419e5] | ||
| - Updated dependencies [22917ab] | ||
| - Updated dependencies [66225bf] |
There was a problem hiding this comment.
| - Updated dependencies [66225bf] |
The commit 66225bf is listed twice in the CLI changelog's "Updated dependencies" section, which creates confusion about which commits were included in this release.
View Details
Analysis
Duplicate commit hash in CLI changelog causes confusion
What fails: The @workflow/cli 4.0.1-beta.3 changelog lists commit 66225bf twice in the "Updated dependencies" section, creating confusion about which commits were included in the release.
How to reproduce:
# View the CLI changelog
cat packages/cli/CHANGELOG.md
# The 4.0.1-beta.3 section shows:# - Updated dependencies [66225bf]# - Updated dependencies [731adff]# - Updated dependencies [57419e5]# - Updated dependencies [22917ab]# - Updated dependencies [66225bf] <-- DUPLICATE# - Updated dependencies [9ba86ce]Result: Same commit hash appears twice (lines 7 and 11 of the reported section), suggesting either a tool bug or metadata issue. Users reading release notes cannot determine if this is intentional or an error.
Expected: Each unique commit hash should appear only once in a package's changelog. Commit 66225bf ("Web: Allow filtering by workflow name and status on the runs list view") should be listed once, not twice. The duplicate was likely generated because 66225bf affected both @workflow/web and @workflow/world-local (two of CLI's dependencies), but the changeset tool should deduplicate commit hashes within a single package's changelog.
Root cause: Commit 66225bf created two changeset files (affecting different packages), and the changelog generation included the commit hash for each dependency update separately, creating a duplicate entry in packages that depend on both.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
mainis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonmain.Releases
@workflow/ai@4.0.1-beta.3
Patch Changes
@workflow/cli@4.0.1-beta.3
Patch Changes
@types/watchpackto be a devDependency@workflow/core@4.0.1-beta.3
Patch Changes
startwhen no args are provided@workflow/next@4.0.1-beta.3
Patch Changes
@workflow/nitro@4.0.1-beta.3
Patch Changes
@workflow/web@4.0.1-beta.3
Patch Changes
workflow@4.0.1-beta.3
Patch Changes
@workflow/world@4.0.1-beta.2
Patch Changes
@types/json-schemadependency (not used)@types/nodefrom being a peerDependencyAuthProviderinterface fromWorldand associated implementations@workflow/world-local@4.0.1-beta.2
Patch Changes
AuthProviderinterface fromWorldand associated implementations@workflow/world-postgres@4.0.1-beta.2
Patch Changes
AuthProviderinterface fromWorldand associated implementations@workflow/world-testing@4.0.1-beta.3
Patch Changes
@workflow/world-vercel@4.0.1-beta.2
Patch Changes
AuthProviderinterface fromWorldand associated implementations