beardthelion e005dda59c ci(release): require backfill release assets to be automation-uploaded ...

The npm backfill republishes GitHub release assets, which are mutable for
anyone with contents: write. Require every asset on the release to have
been uploaded by github-actions[bot], matching the release-author check.
Not a hard bound, but it removes the direct edit path and leaves a review
signal when a hand-uploaded asset blocks a backfill.

2026-09-13 09:03:30 -05:00

..

build-bins.sh

ci: declare the lock-sync toolchain and extend --locked to the shipping builds

2026-07-28 16:28:27 -05:00

build-macos-app.sh

feat: macOS menu bar app for managing gitlawb-node Docker Compose stack (#8)

2026-05-27 09:37:36 +08:00

check-gitlawb-core-deps.sh

ci: declare the lock-sync toolchain and extend --locked to the shipping builds

2026-07-28 16:28:27 -05:00

check-release-versioning.sh

fix(release): scope the annotation check to the [package] table

2026-08-03 09:45:17 -05:00

resolve-release-tag.sh

ci(release): require backfill release assets to be automation-uploaded

2026-09-13 09:03:30 -05:00

test-resolve-release-tag.sh

ci(release): require backfill release assets to be automation-uploaded

2026-09-13 09:03:30 -05:00