fix: regenerate pnpm-lock.yaml to restore JSR tarball URLs (fixes sync-tools)#59
Merged
Merged
Conversation
…l URLs When I regenerated the lockfile for #56 using Homebrew's pnpm 11, the JSR-specific 'tarball:' field was dropped from every @jsr/* resolution entry. CI (pinned to pnpm 9 via packageManager) needs that field because JSR's tarball URL doesn't follow the standard npm convention (uses /~/11/@jsr/name/version.tgz instead of /@jsr/name/-/name-version.tgz). push.yml and release.yml only worked because their cache was warm with the old tarball; sync-tools has no cache and failed on every run since #56 merged. Regenerated with: rm pnpm-lock.yaml && npx -p pnpm@9.15.4 pnpm install --lockfile-only
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
Lockfile regeneration in this PR resolved @biomejs/biome \`^2.3.1\` to 2.4.15, whose formatter no longer multi-lines the \`client.getFeeRateBps(...).catch(...)\` chain in trading.ts. Updated biome.json schema URL to match.
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.
Summary
sync-tools workflow has been failing on every push to main since #56 merged. Root cause: when I regenerated
pnpm-lock.yamlfor #56 using Homebrew's pnpm 11, the JSR-specifictarball:field was dropped from every@jsr/*resolution entry. CI runs pnpm 9.15.4 (perpackageManager), and pnpm 9 needs that field because JSR's tarball URL doesn't follow the standard npm convention:https://npm.jsr.io/@jsr/hk__polymarket/-/hk__polymarket-0.2.1.tgz→ 404https://npm.jsr.io/~/11/@jsr/hk__polymarket/0.2.1.tgz→ 200push.ymlandrelease.ymlonly worked because their pnpm cache was warm with the old tarball;sync-tools.ymlhas no cache step and failed on every run.Latest failed sync-tools run
Fix
Regenerated with the version
packageManageractually pins:rm pnpm-lock.yaml && npx -p pnpm@9.15.4 pnpm install --lockfile-onlyTest plan
Sync MCP Tool Docsrun onmainsucceeds (or stays clean if no doc changes)