webgrip/unfold
5
0
Fork 0
Code Issues 1 Pull requests 2 Projects Releases 54 Packages 8 Wiki Activity Actions

build: stop checking Ploeg's pinned pages in Unfold and let Renovate propose the pin #215

Merged
ryangr0 merged 2 commits from ryangr0/chore/ploeg-docs-and-renovate into development 2026-10-04 08:40:22 +00:00 AGit
Conversation 0 Commits 2 Files changed 10 +78 -26
ryangr0 commented 2026-10-04 08:05:18 +00:00
Owner
Copy link

Two commits that finish separating Unfold from Ploeg after #206.

build(docs): stop applying Unfold's page checks to Ploeg's pinned pages

  • Unfold's docs build no longer checks Ploeg's own pages under apps/ploeg/docs: links, anchors, nav reachability, line anchors and front matter. lychee and Vale skip them too. Ploeg's own mise run docs-check owns those pages.
  • Unfold still renders Ploeg's pages from the pin. A link that doesn't resolve inside a Ploeg page now points at the pinned file on GitHub, so mkdocs --strict stays green.
  • The nav lists only Ploeg's overview, runbook index and configuration reference. Ploeg's runbook index already lists all 12 runbooks; the old nav listed 6.
  • The site and source links name webgrip/unfold.
  • docs/migration.md no longer describes Ploeg's old distribution as current.

build(ploeg): let Renovate propose the Ploeg pin once a week

  • Renovate's git-submodules manager opens a weekly build(ploeg) pull request to the newest commit on Ploeg's main, which .gitmodules now names. The ploeg scope never releases Unfold.
  • These pull requests never merge themselves: each one changes the engine Vloer runs on. There is no soak, because Ploeg's commits are already gated by its CI.
  • Renovate now skips mise's generated .mise lock directories. In #205 it had bumped one of them as if it were a package.
  • ADR-0019 gets two dated bullets recording both changes.

Why: before this, any new or renamed page in Ploeg broke Unfold's docs build when the pin moved. That happened twice during the cutover. Every automated pin bump would have failed the same way.

Evidence

  • I added an unlisted Ploeg page with a broken link and a missing anchor to the submodule's working tree. Today's development fails ("Missing documentation targets"). This branch builds, mkdocs --strict included.
  • mise run verify (all gates), mise run docs-check (513 sources), node scripts/ploeg-pin.mjs --published and renovate-config-validator pass.
  • New docs-rules tests:
    • a Ploeg page is never an orphan;
    • a Ploeg page never needs Unfold's front matter.

Notes

  • The Renovate runner now lists git-submodules, off for every repository that doesn't opt in (homelab-cluster e906a79e). It applies once this merges.
  • A Ploeg bump that changes Ploeg's domain model or ADR ledger fails docs-check on the combined glossary or decision register. The fix is mise run domain and mise run docs-decisions on the branch; the Renovate PR body says so.
  • The runner's mise (2026.7.7) is below this repository's min_version 2026.9.17, so Renovate still can't relock mise tool bumps. docs/operations/ci.md says how to handle that.

🤖 Generated with Claude Code

Two commits that finish separating Unfold from Ploeg after #206. **`build(docs)`: stop applying Unfold's page checks to Ploeg's pinned pages** - Unfold's docs build no longer checks Ploeg's own pages under `apps/ploeg/docs`: links, anchors, nav reachability, line anchors and front matter. lychee and Vale skip them too. Ploeg's own `mise run docs-check` owns those pages. - Unfold still renders Ploeg's pages from the pin. A link that doesn't resolve inside a Ploeg page now points at the pinned file on GitHub, so `mkdocs --strict` stays green. - The nav lists only Ploeg's overview, runbook index and configuration reference. Ploeg's runbook index already lists all 12 runbooks; the old nav listed 6. - The site and source links name `webgrip/unfold`. - `docs/migration.md` no longer describes Ploeg's old distribution as current. **`build(ploeg)`: let Renovate propose the Ploeg pin once a week** - Renovate's `git-submodules` manager opens a weekly `build(ploeg)` pull request to the newest commit on Ploeg's `main`, which `.gitmodules` now names. The `ploeg` scope never releases Unfold. - These pull requests never merge themselves: each one changes the engine Vloer runs on. There is no soak, because Ploeg's commits are already gated by its CI. - Renovate now skips mise's generated `.mise` lock directories. In #205 it had bumped one of them as if it were a package. - ADR-0019 gets two dated bullets recording both changes. **Why:** before this, any new or renamed page in Ploeg broke Unfold's docs build when the pin moved. That happened twice during the cutover. Every automated pin bump would have failed the same way. **Evidence** - I added an unlisted Ploeg page with a broken link and a missing anchor to the submodule's working tree. Today's `development` fails ("Missing documentation targets"). This branch builds, `mkdocs --strict` included. - `mise run verify` (all gates), `mise run docs-check` (513 sources), `node scripts/ploeg-pin.mjs --published` and `renovate-config-validator` pass. - New `docs-rules` tests: - a Ploeg page is never an orphan; - a Ploeg page never needs Unfold's front matter. **Notes** - The Renovate runner now lists `git-submodules`, off for every repository that doesn't opt in (homelab-cluster `e906a79e`). It applies once this merges. - A Ploeg bump that changes Ploeg's domain model or ADR ledger fails docs-check on the combined glossary or decision register. The fix is `mise run domain` and `mise run docs-decisions` on the branch; the Renovate PR body says so. - The runner's mise (2026.7.7) is below this repository's `min_version` 2026.9.17, so Renovate still can't relock mise tool bumps. `docs/operations/ci.md` says how to handle that. 🤖 Generated with [Claude Code](https://claude.com/claude-code) 
Unfold's documentation build checked every page under apps/ploeg/docs
as if Unfold owned it: links, anchors, nav reachability, line anchors
and front matter, plus lychee and Vale. Any new or renamed page in Ploeg
therefore broke Unfold's docs build when the pin moved, as the archived
history pages and the charter page already did.

Ploeg's own docs-check owns those pages now. Unfold still renders them
from the pin; a link that does not resolve in a Ploeg page points at the
pinned file on GitHub, so mkdocs --strict stays green. The nav names only
Ploeg's overview, runbook index and configuration reference. Unfold's own
pages, the combined glossary and the decision register still read Ploeg
at the pin. The site and source links name webgrip/unfold, and the
migration guide stops describing Ploeg's old distribution as current.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
build(ploeg): let Renovate propose the Ploeg pin once a week
All checks were successful
[Workflow] On Pull Request / checks (pull_request) Successful in 5m45s
Details
[Workflow] On Pull Request / ploeg-pin (pull_request) Successful in 33s
Details
[Workflow] On Pull Request / release-policy (pull_request) Successful in 26s
Details
[Workflow] On Pull Request / warnings (pull_request) Successful in 1s
Details
d0cbb3b6cd
 
The pin moved only by hand. Renovate's git-submodules manager now opens
a weekly build(ploeg) pull request to the newest commit on Ploeg's main,
which .gitmodules names. It never merges one itself, since each move
changes the engine Vloer runs on, and Ploeg's CI-gated commits get no
soak. Its body says how to regenerate the combined glossary and the
decision register when Ploeg's model or ADR ledger changed.

Renovate also skips mise's generated .mise lock directories, whose
package.json it bumped as if it were a package in Unfold #205.

The runner must list the manager; homelab-cluster enables it for
repositories that opt in.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ryangr0 merged commit 71ff5558b1 into development 2026-10-04 08:40:22 +00:00
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
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
webgrip/unfold!215
No description provided.