Skip to content

chore(deps): update dependency farcloser/limen to v0.10.0 - #60

Merged
closer-claudio merged 2 commits into
mainfrom
renovate/farcloser-limen-0.x
Oct 10, 2026
Merged

closer-claudio merged 2 commits into
mainfrom
renovate/farcloser-limen-0.x

Conversation

@renovate

@renovate renovate Bot commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
farcloser/limen minor v0.9.0 → v0.10.0

Release Notes

farcloser/limen (farcloser/limen)

v0.10.0

Compare Source

What's Changed

Changes
Dependencies

Full Changelog: farcloser/limen@v0.9.0...v0.10.0


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@closer-claudio closer-claudio mentioned this pull request Oct 7, 2026
@renovate renovate Bot changed the title chore(deps): update dependency farcloser/limen to v0.9.0 chore(deps): update dependency farcloser/limen to v0.9.0 - autoclosed Oct 7, 2026
@renovate renovate Bot closed this Oct 7, 2026
@renovate
renovate Bot deleted the renovate/farcloser-limen-0.x branch October 7, 2026 07:14
closer-claudio
closer-claudio previously approved these changes Oct 7, 2026

@closer-claudio closer-claudio left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Ready at 3cc3439: limen v0.8.0 → v0.9.0. The convergence commit writes exactly v0.9.0's canonical files.

📝 Note

  • What v0.9.0 changes here:
    • security.yaml is content-pinned and reset to limen's (farcloser/limen#266). It runs the root security recipe, which limen fix adds to .justfile.
    • The shared CI lanes ship as the content-pinned reusable limen-verify.yaml (farcloser/limen#263).
    • AGENTS.md gains the read-scope rule (farcloser/limen#268).
    • The Renovate content-pinned rules cover the new files.
    • No tool pin moves: .limen/aqua.yaml and tools/ are unchanged.
  • This repository's own ci.yaml still runs v0.8.0's inline lanes. limen-verify.yaml sits unused until ci.yaml is realigned by hand to call it (v0.9.0's ci.yaml is blob 2eeb2363).
  • The security.yaml this resets was limen's seed byte for byte, so no project lines are lost (C2), and the root security recipe was already there. ci.yaml is the project's edited one (blob 63919da0), so C1 follows the merge. The base is the current main.
  • This duplicates the hand-made #59, which lands the same tree. Closing one of the two is @apostasie's call.

🔍 Verified last

  • The farcloser/limen v0.9.0 checksums, all five archives, match the release asset digests at https://github.com/farcloser/limen/releases/tag/v0.9.0.
  • Every limen-canonical path at this head (.limen/, AGENTS.md, the content-pinned workflows and actions) is blob-identical to v0.9.0's.
  • The convergence commit is by the limen CI app, and GitHub reports it signed.

@renovate renovate Bot changed the title chore(deps): update dependency farcloser/limen to v0.9.0 - autoclosed chore(deps): update dependency farcloser/limen to v0.10.0 Oct 10, 2026
@renovate renovate Bot reopened this Oct 10, 2026
@renovate
renovate Bot force-pushed the renovate/farcloser-limen-0.x branch 20 times, most recently from 49ffc72 to 3b74bba Compare October 10, 2026 07:11
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate
renovate Bot force-pushed the renovate/farcloser-limen-0.x branch from f17eb9a to 93bddee Compare October 10, 2026 07:13
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

@closer-claudio closer-claudio left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ at febaeac: limen v0.10.0 in the project manifest, the App's converge on top, every new checksum the upstream's.

  • 🔍 Checked: two authors on the branch, Renovate's pin commit and the App's chore: refresh checksums and converge the limen baseline (renovate[bot],limen-ci-forkcloser[bot]); .aqua/aqua.yaml moves the one pin to v0.10.0 (and seeds golang/go@go1.27.2 above the import where the repo had none, the #323 design); the 18 checksums .aqua/aqua-checksums.json gains are each one I verified at the source today: limen v0.10.0's five against the release's checksums.txt, go1.27.2's five against go.dev, goreleaser v2.18.3's five against its checksums.txt, ossein v0.3.1 and git-for-windows 2.56.0.2 by download, aqua-registry by download. The other files of the 14 changed are the canonical set (.limen/, the limen workflows, AGENTS.md, the composite actions, release.yml), content-pinned and held to v0.10.0 by the limen lane that is green here. ci and security green at this head: go1.27.2 clears the govulncheck set.

@closer-claudio
closer-claudio merged commit eab286e into main Oct 10, 2026
8 checks passed
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.

1 participant