Skip to content

pins CLI: retire the --js-lock and --package-json legs #99

Description

@lannbot

The npm-git consumption path is retired (#98: the root facade gutted, the setup action's js-locks input removed; the consumer repos migrated to jsr:@polymorph/test in webcrypto#385 / tls#46 / websocket#55 / webrtc-datachannels#162, each with its own runner-js pin gate). The pins subcommand still carries the machinery that served it:

  • pins --js-lock <lockfile> (package-lock/pnpm-lock rev extraction, js_lock_revs),
  • pins bump --package-json (rewriting github:polymorph-components/polymorph-test#<rev> deps),
  • the bump follow-up text printing [--js-lock ...] and npm install guidance.

No consumer passes any of these anymore; they check for a dep shape that no longer exists anywhere. Harmless as dead optional surface, so no urgency — retire them at the next real pins change, and update the bump guidance to the two-mechanism procedure the consumer repos document (cargo rev via pins bump --cargo-toml --workflow; JS via the release version on the @jsr/polymorph__test dep or jsr:@polymorph/test specifier + reinstall). Removing CLI surface is fine under the caret policy at a minor bump, or silently for flags that never appeared in a release's documented interface — decide which applies when the change lands.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions