ci: fix the staging-check infra repo owner; docs: coverage-floor note #9

Open

jfraeys wants to merge 7 commits from docs/cover-floor-wording into main

pull from: docs/cover-floor-wording

merge into: jfraeys:main

jfraeys:main

jfraeys:design/inner-page-headers

jfraeys:jfraeys/fix/staging-check-report

jfraeys:site-separation

Conversation 0 Commits 7 Files changed 3 +36 -63

jfraeys commented 2026-10-18 20:36:54 -04:00

Owner

Copy link

Two small changes:

• ci.yml: staging-check dispatched jfraeysd/infra, an owner that doesn't exist (the repo is jfraeys/infra, which has staging-validate.yml), so every pull-request run failed at its first step with a 404.
• CLAUDE.md: the coverage-floor note named COVER_MIN, the old Makefile variable; it now points at the -min value in ci.yml.

This PR doubles as the first real end-to-end test of staging-check (it provisions an ephemeral Linode node) now that runners reach Forgejo and artifacts upload.

🤖 Generated with Claude Code

https://claude.ai/code/session_01B1FuEx3w8ax6P8QvdxxADM

Two small changes: - **ci.yml:** `staging-check` dispatched `jfraeysd/infra`, an owner that doesn't exist (the repo is `jfraeys/infra`, which has `staging-validate.yml`), so every pull-request run failed at its first step with a 404. - **CLAUDE.md:** the coverage-floor note named `COVER_MIN`, the old Makefile variable; it now points at the `-min` value in `ci.yml`. This PR doubles as the first real end-to-end test of `staging-check` (it provisions an ephemeral Linode node) now that runners reach Forgejo and artifacts upload. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01B1FuEx3w8ax6P8QvdxxADM

jfraeys added 1 commit 2026-10-18 20:36:54 -04:00

docs: point the coverage-floor note at the real setting ... c32e61acc8

CLAUDE.md still named COVER_MIN, the old Makefile variable. The floor is now
the -min value passed to `go run ./cmd/tasks cover` in ci.yml.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B1FuEx3w8ax6P8QvdxxADM

jfraeys added 1 commit 2026-10-18 20:49:22 -04:00

ci: point staging-check at the infra repo's real owner ... 6c37c5bb7a

staging-check dispatched jfraeysd/infra, an owner that doesn't exist (the repo
is jfraeys/infra, where staging-validate.yml lives), so the dispatch call got a
404 and every pull-request CI run failed at its first step.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B1FuEx3w8ax6P8QvdxxADM

jfraeys changed title from docs: point the coverage-floor note at the real setting to ci: fix the staging-check infra repo owner; docs: coverage-floor note 2026-10-18 20:49:28 -04:00

jfraeys added 1 commit 2026-10-18 21:10:44 -04:00

ci: pin govulncheck to a release that builds on Go 1.25 ... 2d8c48a3af

govulncheck@latest (v1.9.0) requires Go 1.26. With the repo on Go 1.25, the go
command downloaded a second toolchain into the module cache, which setup-go
then cached and re-saved as ~600MB on every job; the save failed against the
cache service (500/EBADF) and left jobs hanging at their post steps. v1.7.0 is
the newest release that needs only Go 1.25.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B1FuEx3w8ax6P8QvdxxADM

jfraeys added 1 commit 2026-10-18 21:36:22 -04:00

build: move to Go 1.26.9 to pick up standard-library security fixes ... dcbe223670

govulncheck, run against the Go that actually builds this repo (1.25.13),
reports 13 standard-library vulnerabilities (net/http incl. an HTTP/2 server
crash, net/textproto, crypto/tls, html/template), all fixed in go1.26.9; the
1.25 line gets no fix. Earlier CI runs looked clean only because govulncheck@latest
needed Go 1.26 and so scanned against an auto-downloaded 1.26 toolchain.

go.mod now says go 1.26.9, so CI and the release build (both use
go-version-file: go.mod) compile with a patched standard library, and
govulncheck is pinned to v1.9.0 to match. Verified locally under
GOTOOLCHAIN=go1.26.9: govulncheck reports no vulnerabilities; build, vet,
golangci-lint and the full -race suite with the coverage floor all pass.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B1FuEx3w8ax6P8QvdxxADM

jfraeys added 1 commit 2026-10-19 12:53:42 -04:00

ci: re-run with INFRA_DISPATCH_TOKEN and DEPLOY_* secrets in place ... 5f0240011c

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B1FuEx3w8ax6P8QvdxxADM

jfraeys added 1 commit 2026-10-19 13:15:13 -04:00

ci: find the dispatched infra run via the repo runs list ... 2c7893ff67

Forgejo has no /actions/workflows/<wf>/runs endpoint (404), so curl -f killed
staging-check ~5s after a successful dispatch. List /actions/runs and pick the
first staging-validate run newer than the pre-dispatch max id.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B1FuEx3w8ax6P8QvdxxADM

jfraeys added 1 commit 2026-10-19 14:41:06 -04:00

ci: staging-check dispatches and returns; infra reports back as a commit status ... 77e77ad07a

The infra validation shares one runner with a waiting job, so polling for it
deadlocks. Post staging/validate pending, dispatch with report_repo/report_sha,
and exit; infra's report job posts the final state. Needs the matching
staging-validate.yml change merged in jfraeys/infra first.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B1FuEx3w8ax6P8QvdxxADM

jfraeys referenced this pull request 2026-10-19 17:56:56 -04:00

ci: staging-check echoes INFRA_DISPATCH_TOKEN into the job log (main) #12

jfraeys referenced this pull request 2026-10-19 17:56:57 -04:00

ci: make the staging gate work end to end (status token, required check, stuck-pending timeout) #13

Some checks failed

Hide checks

CI / Test & build (pull_request) Successful in 7m32s

Details

CI / golangci-lint (pull_request) Successful in 2m51s

Details

CI / Build artifacts (pull_request) Successful in 1m57s

Details

CI / Staging deploy check (pull_request) Failing after 1s

Details

This pull request has changes conflicting with the target branch.

• .forgejo/workflows/ci.yml

View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Merge commit title Merge pull request 'ci: fix the staging-check infra repo owner; docs: coverage-floor note' (#9) from docs/cover-floor-wording into main

Merge commit body Reviewed-on: https://git.jfraeys.com/jfraeys/coaching-site/pulls/9

Merge pull request 'ci: fix the staging-check infra repo owner; docs: coverage-floor note' (#9) from docs/cover-floor-wording into main Reviewed-on: https://git.jfraeys.com/jfraeys/coaching-site/pulls/9 Copy merge commit message

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin docs/cover-floor-wording:docs/cover-floor-wording

git switch docs/cover-floor-wording

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main

git merge --no-ff docs/cover-floor-wording

git switch docs/cover-floor-wording

git rebase main

git switch main

git merge --ff-only docs/cover-floor-wording

git switch docs/cover-floor-wording

git rebase main

git switch main

git merge --no-ff docs/cover-floor-wording

git switch main

git merge --squash docs/cover-floor-wording

git switch main

git merge --ff-only docs/cover-floor-wording

git switch main

git merge docs/cover-floor-wording

git push origin main

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

jfraeys/coaching-site!9

No description provided.