4 Commits

Include renames

Author	SHA1	Message	Date
archvillainette	4d03085996	feat(ci): prune release assets outside the newest two tags (#52) (#70) ... Closes #52. Adds `scripts/prune-release-assets.sh` and a best-effort step at the end of `build-binaries.yml`. - Lists every release page, sorts by creation date, skips the newest two published releases, deletes the rest's attachments via `DELETE /releases/{id}/assets/{asset_id}`. - Drafts never consume a keep slot, so a draft cannot strip the newest real release. - Releases, tags, source archives and release notes are never touched. - Nothing is excluded: SHA256SUMS and the wrappers go with the binaries. Checksums are only meaningful next to the files they cover, and the consumer drift-check reads the wrappers from the latest release, which stays complete. - Failures warn and the step has `continue-on-error: true` — a stale asset is cheaper than a blocked publish. `tests/prune-release-assets.sh` drives the script with a stub `curl`: keep window, out-of-order responses, drafts, no non-asset DELETE, short-page pagination stop, and both failure paths. Wired into `make check`. v0.2.0 still needs its 9 assets cleared by hand in the web UI, as the issue notes. 🤖 Generated with [Claude Code](https://claude.com/claude-code)Reviewed-on: #70 Co-authored-by: vickydotbat <vickydotbat@tutamail.com>	2026-07-29 08:51:25 +00:00
archvillainette	b058846e16	chore(ci): consolidate Gitea CI (#47) ... ## Summary - consolidate vet, tests, lint, smoke, and cross-build into one pull-request-only job - keep binary releases strictly v-tag-only with release-only write permission - retain wrapper synchronization only for canonical wrapper changes on main - pin actions and enforce exact trigger contracts ## Verification - nix develop --command make check - trigger mutation contract - 28-workflow cross-repository actionlint audit Generated with Claude CodeReviewed-on: #47 Co-authored-by: vickydotbat <vickydotbat@tutamail.com>	2026-07-22 16:54:26 +00:00
archvillainette	43fe5e0373	Retire the Crucible container image (#41) ... ## Summary The `registry.westgate.pw/deployment/crucible` image has no consumer: `prod.yml` no longer reserves a slot for it (contract settled in sow-platform PR #64) and no runtime or recovery path pulls it. Binaries, wrappers, and the Nix input remain the supported ways to run Crucible. ## What changed - Deleted `.gitea/workflows/build-image.yml`, `publish-image.yml`, `test-image.yml` - Deleted `docker/Dockerfile` and the `make image` target - Updated README, AGENTS.md, and `docs/consumer-contract.md` to state the image is retired Existing `deployment/crucible` images in the registry can be deleted at leisure; nothing references them. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Reviewed-on: #41 Co-authored-by: vickydotbat <vickydotbat@tutamail.com> Co-committed-by: vickydotbat <vickydotbat@tutamail.com>	2026-07-17 07:26:58 +00:00
archvillainette	97f8427c4b	Phase 5: scaffold Crucible (sow-tools) — dispatcher + builder shims, container, PR-first CI, fail-closed (D11, D19).	2026-06-11 20:36:13 +02:00