Repository navigation
chore(deps): bump dependencies and pinned GitHub Actions - #83
Merged
Merged
Conversation
Refresh every dependency to latest except `@noble/hashes`. All bumps are
patch or minor tooling updates.
Runtime deps: none changed, so this is chore-only (no changeset).
Tooling:
- @biomejs/biome 2.5.14 -> 2.5.15
- @commitlint/{cli,config-conventional} 21.2.2 -> 21.2.3
- @types/node 26.6.1 -> 26.6.4
- fs-extra 11.4.0 -> 11.4.1
- knip 6.36.0 -> 6.39.0
- vitest + @vitest/coverage-v8 5.0.1 -> 5.0.3
`@noble/hashes` deliberately stays on ^1.8.0, for the same reason as #75:
bitcoinjs-lib@7.0.2 and bs58check@4.0.0 both declare `@noble/hashes: ^1.2.0`,
so v2 resolves two copies into the tree, and v2 removed the `./sha256`
subpath that `getAddressInfo.ts` imports.
Peer ranges (`@tanstack/query-core` / `@tanstack/react-query` >=5.68.0,
`react` / `react-dom` ^18 || ^19, `bs58` ^6.0.0) already accept the latest
releases and are left as is. pnpm stays on 12.4.2.
Re-pin the three linear-release-action steps from v0.18.0 to the v0.18.1 release SHA. The other pinned actions (checkout v7.0.1, setup-node v7.0.0, pnpm/action-setup v6.1.0, changesets/action v2.1.2) are already latest. v0.18.1 is a patch release. The `action.yml` diff is additive: a new optional `description` input, and the `github_token` default now resolves to empty on GitHub Enterprise only. The installer also verifies the CLI against committed checksums. All inputs this repo uses (`access_key`, `command`, `release_version`, `name`, `links`, `stage`) are unchanged.
|
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
1 participant
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.
Which Linear task is linked to this PR?
None. Routine dependency bump.
Why was it implemented this way?
linear/linear-release-actionto v0.18.1. Other actions are already current. SHA pinning is kept.@noble/hashesat 1.8.0.bitcoinjs-libandbs58checkstill require v1, and v2 removes the./sha256subpath used ingetAddressInfo.ts. Same as chore(deps): bump dependencies, regen lockfile, move to pnpm 12 #75 and chore(deps): bump dependencies and pinned GitHub Actions #79.Visual showcase (Screenshots or Videos)
N/A
Checklist before requesting a review