The npm-publish job is now duplicated verbatim across halos-org/skip (release.yml) and hatlabs/signalk-halpi (release.yml): corepack pin (npm@11.14.1), the npm view <pkg>@$VERSION existence check, checkout/setup-node/build/publish via OIDC trusted publishing. shared-workflows exists to host reusable CI, and everything else in the triad (pr-checks, build-release) is centralized — the npm-publish job is the one piece copy-pasted into a second repo, so the pinned npm version and publish recipe now have to be bumped in N places.
Proposal: add publish-npm.yml (inputs: package-name, node-version) and have both skip and signalk-halpi call it, matching how build-release/pr-checks are shared.
Surfaced in the review of halos-org/skip#228 (maintainability, P3).
The npm-publish job is now duplicated verbatim across
halos-org/skip(release.yml) andhatlabs/signalk-halpi(release.yml): corepack pin (npm@11.14.1), thenpm view <pkg>@$VERSIONexistence check, checkout/setup-node/build/publish via OIDC trusted publishing. shared-workflows exists to host reusable CI, and everything else in the triad (pr-checks, build-release) is centralized — the npm-publish job is the one piece copy-pasted into a second repo, so the pinned npm version and publish recipe now have to be bumped in N places.Proposal: add
publish-npm.yml(inputs:package-name,node-version) and have both skip and signalk-halpi call it, matching how build-release/pr-checks are shared.Surfaced in the review of halos-org/skip#228 (maintainability, P3).