feat!: migrate to unthrown 2.0.0#273
Merged
Merged
Conversation
unthrown 2.0.0 is API-compatible for everything temporal-contract uses (the
`Ok` / `Err` / `Defect` constructors, `TaggedError`, `matchTags`, `fromPromise`
/ `fromSafePromise`, `result.match({ ok, err, defect })`, `.toAsync()`, and the
`result.isOk()` / `isErr()` / `isDefect()` narrowing are all unchanged), so no
source changes were needed — only the `unthrown` / `@unthrown/vitest` catalog
entries bump to 2.0.0 and the published packages' `unthrown` peer range moves
to `^2`.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR upgrades the repo’s unthrown dependency family to 2.0.0 (and aligns published packages’ unthrown peer dependency range to ^2), reflecting the new major version in the workspace catalog, lockfile, docs, and release notes via a changeset.
Changes:
- Bump
unthrownand@unthrown/vitestcatalog versions to2.0.0and refreshpnpm-lock.yaml. - Update published packages’
unthrownpeer dependency range from^1→^2. - Update the migration guide install snippet and add a
majorchangeset covering the package group.
Reviewed changes
Copilot reviewed 6 out of 7 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| pnpm-workspace.yaml | Updates workspace catalog entries for unthrown and @unthrown/vitest to 2.0.0. |
| pnpm-lock.yaml | Lockfile update reflecting unthrown@2.0.0 and @unthrown/vitest@2.0.0. |
| packages/worker/package.json | Updates unthrown peer dependency range to ^2. |
| packages/contract/package.json | Updates unthrown peer dependency range to ^2. |
| packages/client/package.json | Updates unthrown peer dependency range to ^2. |
| docs/guide/migrating-to-unthrown.md | Updates install snippet to unthrown: ^2. |
| .changeset/unthrown-v2.md | Adds a major changeset documenting the unthrown ^2 peer requirement. |
Files not reviewed (1)
- pnpm-lock.yaml: Generated file
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
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.
Summary
Upgrades to
unthrown2.0.0, following the 0.x → 1.0 migrations (#263, #265, all merged).unthrown 2.0.0 is a major release, but its breaking change does not touch anything temporal-contract uses — the public API surface we depend on is identical. So this is effectively a version bump with no source changes.
What changed
unthrown+@unthrown/vitestcatalog entries →2.0.0.unthrownpeer range →^2.^2.majorchangeset (requiringunthrown ^2is breaking for consumers still on 1.x).Unchanged (verified against the new
.d.ts)The
Ok/Err/Defectconstructors,TaggedError,matchTags,fromPromise/fromSafePromise,result.match({ ok, err, defect }),.toAsync(), andresult.isOk()/isErr()/isDefect()narrowing — all identical to 1.0.@unthrown/vitest's matchers (toBeOk/toBeOkWith/toBeErr/toBeDefect) are unchanged too. 2.0.0's additions (isResult,flatTapErr, theAsyncResultcompanion value) are purely additive.Verification
typecheck · oxlint · oxfmt · knip · 271 unit tests · integration tests (exit 0) · docs build — all green, with no code changes required.
🤖 Generated with Claude Code