6 Commits

Include renames

Author	SHA1	Message	Date
claude@clouddev1	6d54c1e96c	ci(publish): wire Scoop bucket + Homebrew tap jobs (D3 §3b/§3c) ... Add sibling publish.yaml jobs (scoop-bucket, homebrew-tap) that render a manifest from the release .sha256 sidecars and idempotently push it to the org-level lazyeval/scoop-bucket and lazyeval/homebrew-tap repos, using the scoped lazyeval-ci bot token (LAZYEVAL_PKG_TOKEN). Render logic lives in dependency-free bash (the CI image has no jq/ruby): scripts/render-scoop-manifest.sh and scripts/render-homebrew-formula.sh. scripts/test-package-renders.sh exercises both: it validates the Scoop JSON with node and asserts fields on both manifests, and additionally runs `ruby -c` on the formula where ruby is present (dev box), skipping it gracefully otherwise. A new ci.yaml `manifests` job runs that test on every push so a render regression surfaces immediately, not at the next manual publish dispatch. The CI image has no ruby, so in CI the gate covers the Scoop JSON (node) and field assertions for both manifests; the formula's Ruby syntax is checked dev-side only (the static heredoc's variable parts cannot introduce syntax errors). - Scoop: x64 (gnu) + arm64 (gnullvm); #/-rename fragment so the bin shim is version-stable; checkver, no autoupdate (the pipeline is the updater). - Homebrew: on_macos/on_linux x arch bare-binary formula; no Windows. Docs: ADR-0056 Amendment 2 (+ README index, requirements D3). Unverified pending real use: scoop/brew install, the HEAD:main branch assumption, macOS Gatekeeper-via-brew on the ad-hoc-signed binary.	2026-06-19 21:30:18 +00:00
claude@clouddev1	ec3c7c304c	ci: enable the cargo fmt --check gate (ADR-ci-002 Amendment 1) ... Adds `cargo fmt --check` (stock defaults) to ci.yaml's gate, now that the tree is rustfmt-clean (commit 41b7e9a). Records that reformat in .git-blame-ignore-revs so `git blame` skips it. Amends ADR-ci-002 (the deferred "revisit on main" fmt decision) + the ci ADR index. Closes #35.	2026-06-17 21:40:58 +00:00
claude@clouddev1	b60c0bb0ec	ci: skip the crate gate for website-only changes ... Add website/** and the website workflow to ci.yaml's paths-ignore, so a push confined to the website subproject (built + published by website.yaml) no longer runs clippy+test. A push that also touches crate code still gates (paths-ignore skips only when all files match).	2026-06-15 20:24:46 +00:00
claude@clouddev1	18d08642d7	ci: skip the gate for docs-only changes ... Add paths-ignore (docs/**, **/*.md) to the gate's push + pull_request triggers so markdown/docs-only changes don't run a full clippy+test that can't change the outcome. Mixed code+docs pushes still gate (not all files are ignored); flake/toolchain changes are deliberately not ignored. Also refresh a stale ADR-0049 -> ADR-ci-002 comment reference.	2026-06-12 22:42:50 +00:00
claude@clouddev1	bba24120f1	ci: scope gate + image-build to branch pushes (skip tags) ... Tag pushes ignore paths: filters, so a release tag spuriously rebuilt the unchanged CI image and re-ran the gate on a commit the branch push already gated. Add branches: ['**'] to both push triggers — tag pushes no longer fire them (release.yaml owns tags). Pushing commits + a tag together still gates the commits via the branch push.	2026-06-12 22:11:24 +00:00
claude@clouddev1	9d8161218a	ci: gate workflow + CI-image build/push, drop probe ... - build-ci-image.yaml: builds .gitea/ci-image/Dockerfile via DinD and pushes git.lazyeval.net/oli/rdbms-playground-ci:latest (REGISTRY_* secrets); triggers on image-input changes + manual dispatch. - ci.yaml: the gate — runs inside that image, clippy -D warnings + cargo test, on push/PR. fmt intentionally not gated (ADR-0049). Removes ci-probe.yaml; it answered the runner questions (jobs run in containers, host nix unreachable, custom container: works).	2026-06-12 21:08:04 +00:00