Skip to content

release: promote develop → main (machine-sizing + Mintlify rebuild + page-coverage CI)#57

Merged
LukasWodka merged 4 commits into
mainfrom
develop
Jun 15, 2026
Merged

release: promote develop → main (machine-sizing + Mintlify rebuild + page-coverage CI)#57
LukasWodka merged 4 commits into
mainfrom
develop

Conversation

@LukasWodka

Copy link
Copy Markdown
Contributor

Summary

Promote develop → main for the docs site. Ships 3 changes to production (docs.tracebloc.io).

What's included (3 commits)

Why merge to main

Per CLAUDE.md, docs is exempt from the develop-only rule (content-only, low-risk) — docs PRs may promote to main directly at Lukas's request. The content has been reviewable on the dev preview (tracebloc-develop.mintlify.app, now rendering all pages after #55).

Review

Dev preview reflects exactly this state: https://tracebloc-develop.mintlify.app/overview/tracebloc

Test plan

  • Review the machine-sizing numbers on the dev preview (environment-setup pages)
  • Merge → Mintlify rebuilds prod (docs.tracebloc.io) within ~1-2 min
  • The new page-coverage CI runs on the main push and confirms all prod pages return 200

🤖 Generated with Claude Code

LukasWodka and others added 3 commits June 6, 2026 18:06
…gate (#54)

The installer now hard-fails below ~5 GB RAM on Linux (was warn-only), so the old
"it only warns" line was wrong. State minimum-to-run (2 CPU / 5 GB / 10 GB) vs
recommended-to-train (4 CPU / 16 GB / 50 GB) consistently across quickstart,
deploy-local, and the setup guide. A single training job reserves ~8 GB.

Pairs with tracebloc/client#217 · refs tracebloc/backend#744

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Mintlify dev preview at tracebloc-develop.mintlify.app was returning 404
on every page that wasn't part of a recent incremental build. Confirmed
by curl: the 3 paths touched by #54 returned 200, all others 404.

Adding a trailing newline to all 31 .mdx files marks them as changed in
git so Mintlify's incremental builder treats every page as needing
update, restoring full dev preview coverage.

No content change — just file-mtime/hash bump.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
)

Catches the failure mode that bit us on 2026-06-06: Mintlify's incremental
build pipeline silently left the dev preview at tracebloc-develop.mintlify.app
serving 404s on most pages for days. Mintlify's own deploy check reported
"success" every time — only an end-to-end HTTP probe of each declared page
would have detected the gap.

The new workflow:
  - Parses docs.json to extract every page path referenced in navigation
  - GETs each path on dev preview and prod docs site (parallel matrix)
  - Fails the job if any page returns non-200
  - Reports broken paths in the workflow summary with the likely fix
    (touch all .mdx files to force Mintlify full rebuild)

Triggers:
  - schedule: 06:00 UTC daily (catches Mintlify state drift)
  - push to develop / main (catches build regressions immediately, with
    a 120s wait for Mintlify deploy to complete)
  - workflow_dispatch with env=dev|prod|both for manual reruns

Reference: docs PR #55 (the force-rebuild fix that surfaced this gap).

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@LukasWodka

Copy link
Copy Markdown
Contributor Author

👋 Heads-up — Code review queue is at 13 / 8

Above the WIP limit. The team convention is to review existing PRs before opening new work.

Open PRs currently in Code review (oldest first):

Pull from review before opening new work. (This is a nudge from the kanban WIP check, not a block.)

…6-04)

docs was exempted from the FR-gate on 2026-06-04 (content-only, low-risk,
may promote develop to main directly). The caller workflow was never
removed, so it kept firing "fail" on every develop to main release PR.
It is not a required status check and the exemption is intentional.

Removing the caller stops the spurious red X on docs release PRs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant