chore: catalog unthrown and its satellites at 5.5.0 - #13
Merged
Conversation
The repo resolved unthrown 5.1.0 while sibling packages are on 5.5.0. Two copies in one graph do not unify — a Result built by one is not assignable to the other's AsyncResult — which surfaced while building @btravstack/config against a local build of this package. Dev resolution only: the peer range is already ^5.0.0, so nothing about what a consumer installs changes. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Updates the pnpm catalog/lockfile to align unthrown and its related tooling packages to the same release train version, avoiding multiple incompatible Result brands in a single dependency graph during local development/builds.
Changes:
- Bump
unthrownfrom5.1.0→5.5.0in the workspace catalog. - Bump
@unthrown/vitestand@unthrown/oxlintfrom5.1.0→5.5.0in the workspace catalog. - Regenerate/update
pnpm-lock.yamlto reflect the catalog upgrades (including updated peer snapshot entries).
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| pnpm-workspace.yaml | Updates catalog versions for unthrown, @unthrown/vitest, and @unthrown/oxlint to 5.5.0 to keep the dev toolchain on a single release train. |
| pnpm-lock.yaml | Lockfile updates to match the new catalog resolutions (package entries + importer snapshots). |
Files not reviewed (1)
- pnpm-lock.yaml: Generated file
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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.
This repo resolved
unthrown5.1.0 while its siblings are on 5.5.0. Two copies in one graph do not unify — aResultbuilt by one is not assignable to the other'sAsyncResult— which is how it surfaced: building@btravstack/configagainst a local build of this package produced brand-mismatch errors that had nothing to do with the code being written.Three catalog entries move together, since they share a release train:
unthrown@unthrown/vitest@unthrown/oxlintDev resolution only.
packages/di's peer range is alreadyunthrown: ^5.0.0, which 5.5.0 satisfies, so nothing about what a consumer installs changes and no package version needs a bump. Onlypnpm-workspace.yamland the lockfile are touched — no file underpackages/.Worth noting for the
@unthrown/oxlinthalf: 5.5.0 carries theno-catch-all-patternself-exemption from btravstack/unthrown#232, so a targeted disable can become an unused one. This repo has none (grepoverpackages/*/srcandexamples/*/srcfinds nono-catch-all-patterncomment), so there is nothing to clean up here.Gate green on the new versions: 10/10 turbo tasks (build, typecheck including the declaration-emit re-check, test), 48 tests, lint and format clean.
Independent of #12 and touching disjoint files, so the two can merge in either order.
🤖 Generated with Claude Code