7 Commits

Include renames

Author	SHA1	Message	Date
mr.zeroandClaude Opus 5	22ee724c09	Run the engine specs before mirroring and publishing ... The engine's 180 specs were never run by CI: the mirror repo is generated by a subtree split, so a pipeline committed there would be overwritten on the next sync, and the monorepo's own pipeline only mirrored and published. A broken engine could reach the gem registry. The test now gates both — it runs on the same trigger the mirror does (a change under libs/ruby/warp_engine), and the steps after it only run if it passes. The specs need MySQL, hence the service, and a prepared test database: on a fresh database maintain_test_schema! reports the engine's own migrations as pending instead of loading the schema. Verified by running the step as written in a clean ruby:3.2 container against a fresh mysql:8 — 180 examples, 0 failures. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-17 07:07:56 +02:00
mr.zeroandClaude Opus 5	2b62070557	Give gem push a named credentials key ... The push prompted for credentials and then died with "404 page not found". Both are the same fault: RubyGems normalizes the keys in ~/.gem/credentials — dots become __ and a trailing slash is appended — so a key written as the host URL can never match the --host value. Finding no key, gem push falls back to signing in against the RubyGems sign_in endpoint, which Gitea does not implement; that is the 404. A named key is stored verbatim and is matched by --key, so the lookup succeeds. Verified against Gem::ConfigFile with both formats. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-16 11:11:17 +02:00
mr.zeroandClaude Opus 5	d11610b6c7	Point the release pipeline at the engines org ... The publishing pipeline was already complete — subtree split to the mirror, gem build and push on a warp_engine-v* tag — but it had never been triggered, and after the org reorganization three of its targets were stale: the mirror push URL and the rubygems registry namespace (twice). The gemspec's allowed_push_host has to match the --host that `gem push` receives, so it now carries the full registry URL rather than the bare forge host, plus source and documentation links. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-16 10:39:40 +02:00
mr.zeroandClaude Fable 5	211dcccbf3	Trim whitespace from the forge token before use ... A trailing newline pasted into the Woodpecker secret broke the push URL ("credential url cannot be parsed"); strip all whitespace from the token in both the mirror and the gem-publish steps. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-08-04 20:07:13 +02:00
mr.zeroandClaude Fable 5	b1b619befa	Allow manual pipeline runs for the split mirror ... Path-filtered push events hide the workflow for unrelated pushes and manual restarts have no changed-files list; add event: manual so the mirror can be triggered from the Woodpecker UI. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-08-04 20:03:35 +02:00
mr.zeroandClaude Fable 5	af779b0988	Fix YAML parse error in the gem-publish step ... The credentials printf line contains ': ' which YAML reads as a mapping; use a literal block scalar for that command. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-08-04 19:57:15 +02:00
mr.zeroandClaude Fable 5	b4d0198d2a	Add CI split-mirror pipeline for WarpEngine ... - .woodpecker.yaml: on master pushes touching libs/ruby/warp_engine, split the subtree and force-push it to the read-only tools/warp_engine mirror; on warp_engine-v* tags, build and push the gem to the Forgejo rubygems registry - engine README documents the monorepo-first workflow and the mirror Requires a `forge_token` Woodpecker secret (repository:write + package:write). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-08-04 19:47:15 +02:00