safe-global / safe-client-gateway / 36544914617

89%

push

github

chore(ci): remove release-please and cut releases by hand (#3522)

Releases are cut by hand from now on: publish a GitHub Release for the tag, or dispatch the Production workflow with a tag. That was the team's preference — cutting tags rather than carrying release commits in the history — and the Release PR mechanism no longer earns its keep next to it.

Deletes the caller `release-please.yml` and the reusable `_release.yml`. Nothing else referenced them.

Also drops `version` from `package.json`. It existed only for release-please's simple mode, which reads the version from there; the package is `private: true` and nothing in the codebase or the workflows imports it. `/about` reports `APPLICATION_VERSION`, which `_build-image.yml` passes as a build arg from the release tag, so the reported version is unaffected. Leaving the field behind would have pinned it at 1.125.0 forever with nothing to bump it.

No change to how production deploys. `production.yml` already triggered on `release: released` and on `workflow_dispatch` with a tag, and both paths stay. Its header comments are updated: it no longer claims release-please publishes the release, the dispatch path is described as an ordinary way to ship a tag rather than only as recovery, and the `released` vs `published` note stops citing `ci.yml`, which the production pipeline PR deleted.

One consequence worth knowing: a `workflow_dispatch` emits no `release` event, so `linear-release.yml` does not run and no release notes are produced. Publishing a GitHub Release keeps both. That is now recorded next to the trigger.

4492 of 5283 branches covered (85.03%)

Branch coverage included in aggregate %.

11481 of 12598 relevant lines covered (91.13%)

545.94 hits per line