Skip to content

Bump limen to v0.3.0 and apply its remediation - #19

Merged
apostasie merged 1 commit into
mainfrom
claudio/20260908-limen-0.3.0
Sep 8, 2026
Merged

Bump limen to v0.3.0 and apply its remediation#19
apostasie merged 1 commit into
mainfrom
claudio/20260908-limen-0.3.0

Conversation

@closer-claudio

Copy link
Copy Markdown
Contributor

Pin moves v0.0.16 → v0.3.0 — five releases. This completes the renovate.json5 migration across both organisations.

Renovate config becomes renovate.json, plain JSON, with "forkProcessing": "enabled".

This repository is the one in the organisation that is not a fork — which is exactly why it is also the only one Renovate has ever run on. blake3, erofs, xz and grid-clock-screensaver were skipped in silence: no PR, no issue, and a green limen check throughout, because the rule validated the config file's contents and nothing about whether Renovate would ever read them. Meanwhile this repo stayed current on golangci-lint, gh and the Go toolchain while the forks drifted.

It also gains the extends reference to the shared preset, which it never carried — this file predates the preset and had been drifting with a private copy of the canonical configuration. config:recommended, the aqua preset, minimumReleaseAge and commitBody are all in the preset now. The organisation's own App identity in gitIgnoredAuthors is kept — that one is the org's, not the preset's.

Baseline: Go-built tools leave aqua for tools/go.mod directives; .limen/, setup-aqua and the checksum workflow reset to v0.3.0 — including the fix for the workflow's commit payload, which was assembled on a command line and died on any convergence past 128 kB. A five-release gap is exactly the size that would have hit it.

just lint and just test green locally.

The pin moves from v0.0.16, five releases. What changes for this repository:

Renovate's per-repository configuration becomes `renovate.json`, plain JSON,
and gains `forkProcessing: "enabled"`. Renovate skips forked repositories by
default under an all-repositories App installation, and it decides that from
the onboarding config file name — renovate.json — read through the platform
API before any preset is resolved, so the setting can live neither in the
shared preset nor in a renovate.json5. This repository is the one in the
organization that is not a fork, which is why it is also the only one Renovate
has ever run on: the other four were skipped in silence, with no pull request,
no issue and a green `limen check` throughout.

The file also gains the `extends` reference to the shared preset, which it
never carried: it predates the preset, and had been drifting with a private
copy of the canonical configuration ever since — config:recommended, the aqua
preset, minimumReleaseAge and commitBody are all in the preset now. The
organization's own App identity in `gitIgnoredAuthors` is kept; it is the
organization's, not the preset's.

The Go-built tools leave aqua for tools/go.mod tool directives, and the
canonical `.limen/` modules, the setup-aqua action and the checksum workflow
reset to the v0.3.0 baseline — including the fix for the workflow's commit
payload, which was built on a command line and died on any convergence past
128 kB. A five-release gap is exactly the size that would have hit it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Signed-off-by: closer-claudio <claudio@farcloser.world>
@apostasie
apostasie merged commit 609d2bb into main Sep 8, 2026
4 checks passed
@apostasie
apostasie deleted the claudio/20260908-limen-0.3.0 branch September 8, 2026 06:00
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.

2 participants