[renovate]

https://entire.io/gh/jdx/mise/trails/453

This PR contains the following updates:

Package	Type	Update	Change
jdx/renovate-config	workflow	patch	v1.0.1 → v1.0.2

---

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

---

Release Notes

jdx/renovate-config (jdx/renovate-config)

v1.0.2: : Lockfile workflows recover when mise.lock is stale

Compare Source

The aube-lock and mise-lock reusable workflows no longer leave Renovate PRs red when a mise tool bump leaves mise.lock with stale platform entries. The preset also stops delaying jdx/workflows updates.

Fixed

• Lockfile workflows now handle a stale mise.lock. When Renovate's mise manager bumps a tool, it rewrites only the version = line in mise.lock, so the per-platform URLs and checksums still point at the old release. On jdx/usage#1520 (aube 2.6.0 → 2.6.1), this broke both workflows. (#​34, @​jdx)

  • aube-lock crashed during setup: mise install --locked failed with aube@2.6.1 is locked to a download URL from 2.6.0. The workflow now refreshes a copy of mise.lock on the runner before installing tools. It never commits that copy, because committing mise.lock is mise-lock's job. Repos with no tracked mise.lock still get a plain mise install.
  • mise-lock could exit successfully but leave a just-published tool's entries on the previous release, then push a lockfile that still failed CI.
  • Both workflows now check the result with mise install --dry-run. If it reports stale entries, they re-run mise lock up to 4 times, waiting 30, 60, then 90 seconds between attempts, and fail with the dry-run output if the entries are still stale. Any other dry-run failure only produces a warning in mise-lock and goes on to the normal install step in aube-lock, so repos that worked before aren't blocked.

  Callers pin these workflows by SHA, so the fix takes effect once Renovate bumps your pin to v1.0.2.

Changed

• jdx/workflows is now on the preset's list of jdx-owned packages exempt from the 7-day minimumReleaseAge, so Renovate bumps it right after each release. (#​33, @​jdx)

Full Changelog: jdx/renovate-config@v1.0.1...v1.0.2

---

Configuration

📅 Schedule: (in timezone America/Chicago)

• Branch creation
  • Only on Tuesday (* * * * 2)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ 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.

[greptile-apps]

This PR does not match any of the 1 configured review trigger rule.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Repository YAML (base), Central YAML (inherited), Organization UI (inherited)
• Review profile: CHILL
• Plan: Advanced
• Run ID: 573c1ba6-4045-492f-83d0-7a282656a3e2

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}