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

build(ploeg): pin Ploeg v0.2.0-rc.1 and follow its releases #216

Merged
ryangr0 merged 1 commit from ryangr0/build/ploeg-pin-release into development 2026-10-04 09:21:01 +00:00 AGit
Conversation 0 Commits 1 Files changed 11 +71 -36
ryangr0 commented 2026-10-04 09:13:11 +00:00
Owner
Copy link

Unfold now pins the latest Ploeg release, release candidates included, instead of a commit on Ploeg's main.

Change

  • Pin: apps/ploeg pins Ploeg v0.2.0-rc.1 (43013502), and .gitmodules names it as branch = v0.2.0-rc.1.
    • That is the first release after the separation. It holds everything the merged replacement PRs needed, plus Ploeg's switch to development as trunk (Ploeg ADR 0064).
  • ploeg-pin --published: requires the gitlink to be the commit of the release tag .gitmodules names, on github.com/ploeg-hq/ploeg.
    • It used to require the pin to be on Ploeg's main. Ploeg candidates now sit on its development branch, so that rule could no longer hold.
    • Run locally, the check requires a release tag name.
  • Renovate: reads the tag and compares release tags as semver, with ignoreUnstable: false. It opens a build(ploeg) pull request for each newer release, candidates included. There is no schedule (releases are deliberate) and it never merges by itself.
  • Docs: ADR-0019 gets a dated bullet, and the CI guide and AGENTS.md describe the release pin. The decision register picks up Ploeg ADR 0064.

Checks

  • scripts/ploeg-pin.test.mjs: 6 tests. The release-tag and release-commit tests fail against the old script.
  • mise run verify (all gates) and mise run docs-check (516 sources) pass.
  • node scripts/ploeg-pin.mjs --published reports "is release v0.2.0-rc.1", and renovate-config-validator passes.
  • The v0.2.0-rc.1 assets match SHA256SUMS, and source-commit.txt names 43013502.

🤖 Generated with Claude Code

Unfold now pins the latest Ploeg **release**, release candidates included, instead of a commit on Ploeg's `main`. ## Change - **Pin:** `apps/ploeg` pins Ploeg `v0.2.0-rc.1` (`43013502`), and `.gitmodules` names it as `branch = v0.2.0-rc.1`. - That is the first release after the separation. It holds everything the merged replacement PRs needed, plus Ploeg's switch to `development` as trunk (Ploeg ADR 0064). - **`ploeg-pin --published`:** requires the gitlink to be the commit of the release tag `.gitmodules` names, on `github.com/ploeg-hq/ploeg`. - It used to require the pin to be on Ploeg's `main`. Ploeg candidates now sit on its `development` branch, so that rule could no longer hold. - Run locally, the check requires a release tag name. - **Renovate:** reads the tag and compares release tags as semver, with `ignoreUnstable: false`. It opens a `build(ploeg)` pull request for each newer release, candidates included. There is no schedule (releases are deliberate) and it never merges by itself. - **Docs:** ADR-0019 gets a dated bullet, and the CI guide and `AGENTS.md` describe the release pin. The decision register picks up Ploeg ADR 0064. ## Checks - `scripts/ploeg-pin.test.mjs`: 6 tests. The release-tag and release-commit tests fail against the old script. - `mise run verify` (all gates) and `mise run docs-check` (516 sources) pass. - `node scripts/ploeg-pin.mjs --published` reports "is release v0.2.0-rc.1", and `renovate-config-validator` passes. - The `v0.2.0-rc.1` assets match `SHA256SUMS`, and `source-commit.txt` names `43013502`. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
build(ploeg): pin Ploeg v0.2.0-rc.1 and follow its releases
All checks were successful
[Workflow] On Pull Request / ploeg-pin (pull_request) Successful in 26s
Details
[Workflow] On Pull Request / release-policy (pull_request) Successful in 24s
Details
[Workflow] On Pull Request / checks (pull_request) Successful in 5m51s
Details
[Workflow] On Pull Request / warnings (pull_request) Successful in 0s
Details
5b3073e9ca
 
The owner wants Unfold on the latest Ploeg release, release candidates
included, instead of a commit on Ploeg's main. Ploeg now tags candidates
on its development trunk (Ploeg ADR 0064) and published v0.2.0-rc.1, which
holds every change Unfold's replacements needed.

.gitmodules names the release tag (branch = v0.2.0-rc.1). The ploeg-pin
job requires the gitlink to be that tag's commit on github.com/ploeg-hq/
ploeg; locally the check requires a release tag name. Renovate reads the
tag, compares release tags as semver with ignoreUnstable off, and proposes
each newer release, candidates included, without a schedule. ADR-0019
records the change; the decision register picks up Ploeg ADR 0064.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ryangr0 merged commit 299f0a6a5e into development 2026-10-04 09:21:01 +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!216
No description provided.