uhhm/varde
1
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 10 Wiki Activity
38 Commits 1 Branch 11 Tags
73228125245714098f29a43addb6e7d326b91ecb
Commit Graph
5 Commits
Author SHA1 Message Date
Bendik Aagaard LynghaugandClaude Opus 4.8 4ff007e403 ci: v4 builtin:checkout in ci + release (no Node, no token-in-URL)
ci / quality (push) Failing after 53s
Details 
builtin:checkout is native Go, so the rust:1 container needs no Node and the
job token no longer rides in the fetch URL (was visible in process args).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
 2026-09-28 13:39:06 +02:00
Bendik LynghaugandClaude Fable 5 b53b5cc000 Bound every await in push_to; plain-git checkout for real this time
ci / quality (push) Failing after 3m0s
Details 
CI (run 208) showed the Push RPC hanging past the test client's 120s
read timeout: endpoint.connect and the delivery-verification observe
loop had no bounds, so a wedged path hung the socket instead of
failing. Connect now times out at 30s and each observe step at 60s,
producing structured errors that name the stage.

The checkout action is back out: run 212 proved the failure is not the
action's version — the runner execs the action's JS with node inside
the job container, and rust:1 has no node ('exec: "node": executable
file not found'). Plain git needs nothing the container lacks.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
 2026-08-16 15:39:58 +02:00
Bendik LynghaugandClaude Fable 5 a1fc85b62d Workflows: back to actions/checkout, on v5
ci / quality (push) Failing after 15s
Details 
The v4 pin was the problem, not the action; use the current major.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
 2026-08-16 15:12:48 +02:00
Bendik LynghaugandClaude Fable 5 19fb9de7d9 Workflows: replace actions/checkout with plain git
ci / quality (push) Failing after 4m11s
Details 
The runner failed resolving/running the external checkout action; a
git fetch of GITHUB_SHA with the workflow token needs neither action
resolution nor a node runtime in the job container, and works against
the private repo. Also document that a bare `cargo release` tags the
current version (the path for 0.1.0, which is already the workspace
version).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
 2026-08-16 15:11:55 +02:00
Bendik LynghaugandClaude Fable 5 c52c3b1238 Release pipeline: cargo-release config + Gitea Actions workflows
ci / quality (push) Failing after 1m15s
Details 
- release.toml: one shared workspace version, single vX.Y.Z tag,
  full test suite as the pre-release gate, no crates.io publishing.
- .gitea/workflows/ci.yml: the Woodpecker quality bar (fmt, clippy
  -D warnings, tests) for repos served by act_runner.
- .gitea/workflows/release.yml: on a version tag, build stripped
  release binaries for x86_64 and aarch64 Linux, bundle them with the
  systemd units, rendered man pages and example config, and attach the
  tarballs (+ sha256) to a Gitea release via the API.
- dist/PKGBUILD: point at the repo's new home on project.uhhm.no.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
 2026-08-16 14:54:17 +02:00