Skip to content

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

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

apostasie merged 1 commit into
mainfrom
claudio/20260908-limen-0.3.0

Conversation

@closer-claudio

Copy link
Copy Markdown
Contributor

Pin moves v0.1.2 → v0.3.0. Supersedes #43, which cannot go green on its own — see below.

What changes

Renovate config becomes renovate.json, plain JSON, with "forkProcessing": "enabled". Renovate skips forked repositories by default under an all-repositories App installation, and decides that from the onboarding config file name — renovate.json — fetched through the platform API before any preset is resolved. A renovate.json5 is accepted as configuration and ignored for that, so the setting can live neither in the shared preset nor in the old file.

The old file held the seed and nothing project-specific, so nothing needed porting. It is deleted rather than left beside the new one, where Renovate would read whichever it found first.

Go-built tools leave aqua for tools/go.mod tool directives, and the canonical .limen/ modules, setup-aqua action and checksum workflow reset to the v0.3.0 baseline.

Why #43 is red, and why this fixes it

Nothing was wrong with #43's contents. The update job died:

/usr/bin/jq: Argument list too long

The checksum workflow built its GraphQL commit payload on a command line. A converged baseline here is 118,635 bytes — ~158 kB once base64'd — against Linux's MAX_ARG_STRLEN of 131,072. So jq never produced the mutation, aqua-checksums.json never got its v0.2.1 entry, and just lint then failed before its first recipe:

▶ lint: limen
aqua failed … package_version=v0.2.1 error="checksum is required"

The workflow cannot ship its own fix — the workflow that runs on a branch is the one already on that branch, so every Renovate bump here would keep dying the same way. The repaired copy (payload built on disk via --rawfile/--slurpfile/--data-binary @file) arrives as part of this convergence, committed directly rather than by the broken job.

just lint and just test green locally.

The pin moves from v0.1.2. 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 — fetched through the
platform API before any preset is resolved. A renovate.json5 is accepted as
configuration and ignored for that, so the setting could not be inherited
from the shared preset nor carried by the old file. The old file's content
was the seed with nothing project-specific, so nothing needed porting; it is
deleted rather than left beside the new one, where Renovate would read
whichever it found first.

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.

That last one matters here. This repository's aqua-bump branch was red, and
not for anything in the branch: the checksum workflow built its commit
payload on a command line, and a converged baseline is ~160 kB base64 against
Linux's 128 kB per-argument limit, so `jq` died with "Argument list too long",
the checksum was never written, and `just lint` could not install limen at
all — "checksum is required", failing before its first recipe. The workflow
cannot ship its own fix, since the workflow that runs on a branch is the one
already on it; the fixed copy arrives here as part of this convergence.

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