Skip to content

fix(deps): refresh package-lock for libsodium 0.7.16 - #5

Merged
adacapo21 merged 1 commit into
mainfrom
fix/lockfile-libsodium-0.7.16
Apr 29, 2026
Merged

fix(deps): refresh package-lock for libsodium 0.7.16#5
adacapo21 merged 1 commit into
mainfrom
fix/lockfile-libsodium-0.7.16

Conversation

@adacapo21

Copy link
Copy Markdown
Member

Summary

  • package.json was bumped to libsodium-sumo@^0.7.16 and libsodium-wrappers-sumo@^0.7.16 without regenerating package-lock.json, which still resolved both to 0.7.15.
  • npm ci on main rejects the lockfile because ^0.7.16 does not satisfy 0.7.15. Failing run: https://github.com/IndigoProtocol/cardano-mcp/actions/runs/23770982837
  • This PR regenerates the lockfile (npm install --package-lock-only) so the two packages resolve to 0.7.16.

Test plan

  • npm ci succeeds locally
  • npm run build succeeds locally
  • CI build (20.x) passes
  • CI build (22.x) passes

package.json was bumped to libsodium-sumo@^0.7.16 and
libsodium-wrappers-sumo@^0.7.16 without regenerating the lockfile,
which still pinned 0.7.15. npm ci on main started failing with:

  Invalid: lock file's libsodium-sumo@0.7.15 does not satisfy
  libsodium-sumo@0.7.16

Regenerate the lockfile so npm ci succeeds again.
@adacapo21
adacapo21 merged commit c9ff7b6 into main Apr 29, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant