Repository navigation
limen v0.9.0 - #49
Merged
Merged
limen v0.9.0#49
Conversation
By hand: Renovate opened no v0.9.0 bump for this repository. `just do tools set farcloser/limen v0.9.0`, then `limen fix` and `aqua update-checksum --prune`: AGENTS.md, .limen/renovate.json and security.yaml reset to v0.9.0 (security.yaml is content-pinned now and runs `just security`; the old one had no project line to keep), and .github/workflows/limen-verify.yaml is written. ci.yaml is the project's own and does not call limen-verify.yaml yet; that is its own change (C1). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: closer-claudio <claudio@farcloser.world>
closer-claudio
commented
Oct 7, 2026
closer-claudio
left a comment
closer-claudio
left a comment
Contributor
Author
There was a problem hiding this comment.
✅ at 8f095c8: limen v0.8.0 → v0.9.0 by hand. It lands exactly where Renovate's converge would.
🔍 Checked:
- Every limen-canonical path at this head is blob-identical to the v0.9.0 tag's:
limen-verify.yaml,security.yaml,.limen/*andAGENTS.md. - The five
farcloser/limenv0.9.0 checksums match the release asset digests. - The old
security.yamlwas limen's seed byte for byte (C2), and the rootsecurityrecipe is present. ci.yamlis the project's edited one (blob642b9bc0), so C1 follows.- The base is the current main, and the commit is signed.
📝 This duplicates Renovate's #50, which it opened about 30 s after this one. The dashboard held it under "Pending Status Checks", so Renovate hadn't skipped it. Whichever of the two merges first makes the other redundant. Closing one is @apostasie's call.
apostasie
approved these changes
Oct 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🎯 Why: get every forkcloser repository on limen v0.9.0 (@apostasie). Renovate opened no bump for curl.
🛠️ What:
just do tools set farcloser/limen v0.9.0,limen fix,aqua update-checksum --prune. ci.yaml's switch to limen-verify.yaml (C1) follows in its own PR.🧪 How:
limen fixresolves every rule. C2: security.yaml had no project line (diffed against v0.9.0's canonical). Green locally:just lint, plusjust testwhere the repository has tests. U: links (sandbox) where noted.