NexusMutual / smart-contracts / #1764

81%

release-candidate: 81%

Pull #1530

build: move the release onto the sdk model

Mirrors the change made in rwi-vault, adopting the shape sdk already uses.

- one release.yml entry point with a channel input, replacing release.yml
  and release-next.yml. npm trusted publishing authorises a workflow file
  rather than a repository, so both channels have to publish from one file.
- publishing over OIDC. NPM_TOKEN is gone, along with the two
  deployments:publish scripts that would otherwise offer a second,
  unbuilt path to the registry. Node 22 ships npm 10, which predates
  trusted publishing, so the publish job upgrades npm first.
- prep-latest.yml and prep-next.yml as local reusable workflows, each
  building the deployments package and uploading it. The publish job
  ships that artifact rather than rebuilding, so what reaches npm is what
  was built.

The branch flow is unchanged: the bump still lands on release-candidate
and is fast-forwarded to master. sdk bumps on master and rebases back,
which suits a repo whose integration branch is dev; here it would mean
force-pushing release-candidate for no gain.

The shared workflows stay pinned at @master. The pnpm branch that
rwi-vault and sdk pin hardcodes pnpm, and this repo uses npm.

1285 of 1726 branches covered (74.45%)

Branch coverage included in aggregate %.

2451 of 2909 relevant lines covered (84.26%)

145.85 hits per line