Skip to content

chore(deps): update dependency aube to latest - #1520

Merged
renovate[bot] merged 2 commits into
mainfrom
renovate/mise-non-major
Sep 30, 2026
Merged

renovate[bot] merged 2 commits into
mainfrom
renovate/mise-non-major

Conversation

@renovate

@renovate renovate Bot commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

https://entire.io/gh/jdx/usage/trails/66

This PR contains the following updates:

Package Type Update Change
aube tools patch 2.6.0 → v2.6.1

Warning

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


Release Notes

jdx/aube (aube)

v2.6.1: : Maintenance release

Compare Source

The commit range for this release has no user-facing changes.

Full Changelog: aubepkg/aube@bd94e42...v2.6.1

💚 Sponsor aube

aube is built and maintained by @​jdx, an open source developer at entire.io, the title sponsor of his open source work.

If aube saves your team install time or CI minutes, please consider becoming an individual or company sponsor. Your support funds ongoing development and helps keep aube fast, free, and independent.


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.

@renovate
renovate Bot enabled auto-merge (squash) September 29, 2026 22:30
@greptile-apps

greptile-apps Bot commented Sep 29, 2026

Copy link
Copy Markdown
Contributor

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

@coderabbitai

coderabbitai Bot commented Sep 29, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

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

⚙️ Run configuration

Configuration used: Central YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Advanced

Run ID: 0bc399db-ab60-4e47-85fb-651a2cf88ec6

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

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

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

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@renovate
renovate Bot merged commit c329f5f into main Sep 30, 2026
14 checks passed
@renovate
renovate Bot deleted the renovate/mise-non-major branch September 30, 2026 00:42
mise-en-dev added a commit that referenced this pull request Oct 6, 2026
<!-- entire-trail-link-start -->
https://entire.io/gh/jdx/usage/trails/58
<!-- entire-trail-link-end -->

### ⚡ Performance

- reduce development debug info by [@jdx](https://github.com/jdx) in
[#1525](#1525)

### 🧪 Testing

- **(lib)** support independently enabled optional features by
[@jdx](https://github.com/jdx) in
[#1513](#1513)

### 🛡️ Security

- restrict AI replies on Discussions and Issues and note the instant ban
by [@jdx](https://github.com/jdx) in
[#1522](#1522)

### 🔍 Other Changes

- **(entire)** store checkpoints in a private repository by
[@jdx](https://github.com/jdx) in
[190ff3e](190ff3e)
- **(entire)** commit codex session hooks by
[@jdx](https://github.com/jdx) in
[abee1b8](abee1b8)
- **(entire)** commit claude session hooks by
[@jdx](https://github.com/jdx) in
[364d74e](364d74e)
- **(entire)** restore lower-cost trail findings by
[@jdx](https://github.com/jdx) in
[2f2f991](2f2f991)
- limit each contributor to one open draft PR by
[@jdx](https://github.com/jdx) in
[#1519](#1519)
- add hk pre-commit hook by [@jdx](https://github.com/jdx) in
[#1523](#1523)
- update pr-closer policy by [@jdx](https://github.com/jdx) in
[a2608b7](a2608b7)

### 📦️ Dependency Updates

- update ubuntu:26.04 docker digest to da6fc2b by
[@renovate[bot]](https://github.com/renovate[bot]) in
[#1514](#1514)
- update jdx/renovate-config action to v1.0.1 by
[@renovate[bot]](https://github.com/renovate[bot]) in
[#1515](#1515)
- update mise tools to latest by
[@renovate[bot]](https://github.com/renovate[bot]) in
[#1516](#1516)
- update dependency communique to latest by
[@renovate[bot]](https://github.com/renovate[bot]) in
[#1518](#1518)
- update dependency aube to latest by
[@renovate[bot]](https://github.com/renovate[bot]) in
[#1520](#1520)
- run go mod tidy on Renovate branches by [@jdx](https://github.com/jdx)
in [#1521](#1521)
- update module github.com/urfave/cli/v3 to v3.13.0 by
[@renovate[bot]](https://github.com/renovate[bot]) in
[#1517](#1517)
- lock file maintenance by
[@renovate[bot]](https://github.com/renovate[bot]) in
[#1524](#1524)
- update dependency golangci-lint to v2.14.0 by
[@renovate[bot]](https://github.com/renovate[bot]) in
[#1526](#1526)
- update jdx/mise-action action to v5 by
[@renovate[bot]](https://github.com/renovate[bot]) in
[#1527](#1527)
renovate Bot added a commit to jdx/packslip that referenced this pull request Oct 6, 2026
This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [jdx/renovate-config](https://redirect.github.com/jdx/renovate-config)
| workflow | patch | `v1.0.1` → `v1.0.2` |

---

### Release Notes

<details>
<summary>jdx/renovate-config (jdx/renovate-config)</summary>

###
[`v1.0.2`](https://redirect.github.com/jdx/renovate-config/releases/tag/v1.0.2):
: Lockfile workflows recover when mise.lock is stale

[Compare
Source](https://redirect.github.com/jdx/renovate-config/compare/v1.0.1...v1.0.2)

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](https://redirect.github.com/jdx/usage/issues/1520)
(aube 2.6.0 → 2.6.1), this broke both workflows.
([#&#8203;34](https://redirect.github.com/jdx/renovate-config/issues/34),
[@&#8203;jdx](https://redirect.github.com/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.
([#&#8203;33](https://redirect.github.com/jdx/renovate-config/issues/33),
[@&#8203;jdx](https://redirect.github.com/jdx))

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

</details>

---

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

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/jdx/packslip).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xMzQuMSIsInVwZGF0ZWRJblZlciI6IjQ0LjEzNC4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
jdx pushed a commit to jdx/usage-sh that referenced this pull request Oct 6, 2026
This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [jdx/renovate-config](https://redirect.github.com/jdx/renovate-config)
| workflow | patch | `v1.0.1` → `v1.0.2` |

---

### Release Notes

<details>
<summary>jdx/renovate-config (jdx/renovate-config)</summary>

###
[`v1.0.2`](https://redirect.github.com/jdx/renovate-config/releases/tag/v1.0.2):
: Lockfile workflows recover when mise.lock is stale

[Compare
Source](https://redirect.github.com/jdx/renovate-config/compare/v1.0.1...v1.0.2)

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](https://redirect.github.com/jdx/usage/issues/1520)
(aube 2.6.0 → 2.6.1), this broke both workflows.
([#&#8203;34](https://redirect.github.com/jdx/renovate-config/issues/34),
[@&#8203;jdx](https://redirect.github.com/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.
([#&#8203;33](https://redirect.github.com/jdx/renovate-config/issues/33),
[@&#8203;jdx](https://redirect.github.com/jdx))

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

</details>

---

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

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/jdx/usage-sh).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xMzQuMSIsInVwZGF0ZWRJblZlciI6IjQ0LjEzNC4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
jdx pushed a commit to jdx/mise-versions that referenced this pull request Oct 6, 2026
<!-- entire-trail-link-start -->
https://entire.io/gh/jdx/mise-versions/trails/36
<!-- entire-trail-link-end -->

This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [jdx/renovate-config](https://redirect.github.com/jdx/renovate-config)
| workflow | patch | `v1.0.1` → `v1.0.2` |

---

### Release Notes

<details>
<summary>jdx/renovate-config (jdx/renovate-config)</summary>

###
[`v1.0.2`](https://redirect.github.com/jdx/renovate-config/releases/tag/v1.0.2):
: Lockfile workflows recover when mise.lock is stale

[Compare
Source](https://redirect.github.com/jdx/renovate-config/compare/v1.0.1...v1.0.2)

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](https://redirect.github.com/jdx/usage/issues/1520)
(aube 2.6.0 → 2.6.1), this broke both workflows.
([#&#8203;34](https://redirect.github.com/jdx/renovate-config/issues/34),
[@&#8203;jdx](https://redirect.github.com/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.
([#&#8203;33](https://redirect.github.com/jdx/renovate-config/issues/33),
[@&#8203;jdx](https://redirect.github.com/jdx))

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

</details>

---

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

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/jdx/mise-versions).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xMzQuMSIsInVwZGF0ZWRJblZlciI6IjQ0LjEzNC4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate Bot added a commit to jdx/pitchfork that referenced this pull request Oct 6, 2026
This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [jdx/renovate-config](https://redirect.github.com/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

<details>
<summary>jdx/renovate-config (jdx/renovate-config)</summary>

###
[`v1.0.2`](https://redirect.github.com/jdx/renovate-config/releases/tag/v1.0.2):
: Lockfile workflows recover when mise.lock is stale

[Compare
Source](https://redirect.github.com/jdx/renovate-config/compare/v1.0.1...v1.0.2)

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](https://redirect.github.com/jdx/usage/issues/1520)
(aube 2.6.0 → 2.6.1), this broke both workflows.
([#&#8203;34](https://redirect.github.com/jdx/renovate-config/issues/34),
[@&#8203;jdx](https://redirect.github.com/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.
([#&#8203;33](https://redirect.github.com/jdx/renovate-config/issues/33),
[@&#8203;jdx](https://redirect.github.com/jdx))

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

</details>

---

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

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/jdx/pitchfork).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xMzQuMSIsInVwZGF0ZWRJblZlciI6IjQ0LjEzNC4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
renovate Bot added a commit to jdx/mise that referenced this pull request Oct 6, 2026
This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [jdx/renovate-config](https://redirect.github.com/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

<details>
<summary>jdx/renovate-config (jdx/renovate-config)</summary>

###
[`v1.0.2`](https://redirect.github.com/jdx/renovate-config/releases/tag/v1.0.2):
: Lockfile workflows recover when mise.lock is stale

[Compare
Source](https://redirect.github.com/jdx/renovate-config/compare/v1.0.1...v1.0.2)

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](https://redirect.github.com/jdx/usage/issues/1520)
(aube 2.6.0 → 2.6.1), this broke both workflows.
([#&#8203;34](https://redirect.github.com/jdx/renovate-config/issues/34),
[@&#8203;jdx](https://redirect.github.com/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.
([#&#8203;33](https://redirect.github.com/jdx/renovate-config/issues/33),
[@&#8203;jdx](https://redirect.github.com/jdx))

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

</details>

---

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

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/jdx/mise).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xMzQuMSIsInVwZGF0ZWRJblZlciI6IjQ0LjEzNC4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
renovate Bot added a commit that referenced this pull request Oct 6, 2026
<!-- entire-trail-link-start -->
https://entire.io/gh/jdx/usage/trails/74
<!-- entire-trail-link-end -->

This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [jdx/renovate-config](https://redirect.github.com/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

<details>
<summary>jdx/renovate-config (jdx/renovate-config)</summary>

###
[`v1.0.2`](https://redirect.github.com/jdx/renovate-config/releases/tag/v1.0.2):
: Lockfile workflows recover when mise.lock is stale

[Compare
Source](https://redirect.github.com/jdx/renovate-config/compare/v1.0.1...v1.0.2)

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
[#1520](https://redirect.github.com/jdx/usage/issues/1520)
(aube 2.6.0 → 2.6.1), this broke both workflows.
([#&#8203;34](https://redirect.github.com/jdx/renovate-config/issues/34),
[@&#8203;jdx](https://redirect.github.com/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.
([#&#8203;33](https://redirect.github.com/jdx/renovate-config/issues/33),
[@&#8203;jdx](https://redirect.github.com/jdx))

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

</details>

---

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

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/jdx/usage).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xMzQuMSIsInVwZGF0ZWRJblZlciI6IjQ0LjEzNC4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
renovate Bot added a commit to jdx/communique that referenced this pull request Oct 6, 2026
<!-- entire-trail-link-start -->
https://entire.io/gh/jdx/communique/trails/35
<!-- entire-trail-link-end -->

This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [jdx/renovate-config](https://redirect.github.com/jdx/renovate-config)
| workflow | patch | `v1.0.1` → `v1.0.2` |

---

### Release Notes

<details>
<summary>jdx/renovate-config (jdx/renovate-config)</summary>

###
[`v1.0.2`](https://redirect.github.com/jdx/renovate-config/releases/tag/v1.0.2):
: Lockfile workflows recover when mise.lock is stale

[Compare
Source](https://redirect.github.com/jdx/renovate-config/compare/v1.0.1...v1.0.2)

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](https://redirect.github.com/jdx/usage/issues/1520)
(aube 2.6.0 → 2.6.1), this broke both workflows.
([#&#8203;34](https://redirect.github.com/jdx/renovate-config/issues/34),
[@&#8203;jdx](https://redirect.github.com/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.
([#&#8203;33](https://redirect.github.com/jdx/renovate-config/issues/33),
[@&#8203;jdx](https://redirect.github.com/jdx))

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

</details>

---

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

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/jdx/communique).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xMzQuMSIsInVwZGF0ZWRJblZlciI6IjQ0LjEzNC4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate Bot added a commit to jdx/tak that referenced this pull request Oct 6, 2026
<!-- entire-trail-link-start -->
https://entire.io/gh/jdx/tak/trails/65
<!-- entire-trail-link-end -->

This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [jdx/renovate-config](https://redirect.github.com/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

<details>
<summary>jdx/renovate-config (jdx/renovate-config)</summary>

###
[`v1.0.2`](https://redirect.github.com/jdx/renovate-config/releases/tag/v1.0.2):
: Lockfile workflows recover when mise.lock is stale

[Compare
Source](https://redirect.github.com/jdx/renovate-config/compare/v1.0.1...v1.0.2)

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](https://redirect.github.com/jdx/usage/issues/1520)
(aube 2.6.0 → 2.6.1), this broke both workflows.
([#&#8203;34](https://redirect.github.com/jdx/renovate-config/issues/34),
[@&#8203;jdx](https://redirect.github.com/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.
([#&#8203;33](https://redirect.github.com/jdx/renovate-config/issues/33),
[@&#8203;jdx](https://redirect.github.com/jdx))

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

</details>

---

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

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job log](https://developer.mend.io/github/jdx/tak).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xMzQuMSIsInVwZGF0ZWRJblZlciI6IjQ0LjEzNC4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate Bot added a commit to jdx/fnox that referenced this pull request Oct 6, 2026
This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [jdx/renovate-config](https://redirect.github.com/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

<details>
<summary>jdx/renovate-config (jdx/renovate-config)</summary>

###
[`v1.0.2`](https://redirect.github.com/jdx/renovate-config/releases/tag/v1.0.2):
: Lockfile workflows recover when mise.lock is stale

[Compare
Source](https://redirect.github.com/jdx/renovate-config/compare/v1.0.1...v1.0.2)

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](https://redirect.github.com/jdx/usage/issues/1520)
(aube 2.6.0 → 2.6.1), this broke both workflows.
([#&#8203;34](https://redirect.github.com/jdx/renovate-config/issues/34),
[@&#8203;jdx](https://redirect.github.com/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.
([#&#8203;33](https://redirect.github.com/jdx/renovate-config/issues/33),
[@&#8203;jdx](https://redirect.github.com/jdx))

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

</details>

---

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

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/jdx/fnox).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xMzQuMSIsInVwZGF0ZWRJblZlciI6IjQ0LjEzNC4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
renovate Bot added a commit to jdx/hk that referenced this pull request Oct 6, 2026
This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [jdx/renovate-config](https://redirect.github.com/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

<details>
<summary>jdx/renovate-config (jdx/renovate-config)</summary>

###
[`v1.0.2`](https://redirect.github.com/jdx/renovate-config/releases/tag/v1.0.2):
: Lockfile workflows recover when mise.lock is stale

[Compare
Source](https://redirect.github.com/jdx/renovate-config/compare/v1.0.1...v1.0.2)

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](https://redirect.github.com/jdx/usage/issues/1520)
(aube 2.6.0 → 2.6.1), this broke both workflows.
([#&#8203;34](https://redirect.github.com/jdx/renovate-config/issues/34),
[@&#8203;jdx](https://redirect.github.com/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.
([#&#8203;33](https://redirect.github.com/jdx/renovate-config/issues/33),
[@&#8203;jdx](https://redirect.github.com/jdx))

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

</details>

---

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

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job log](https://developer.mend.io/github/jdx/hk).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xMzQuMSIsInVwZGF0ZWRJblZlciI6IjQ0LjEzNC4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
renovate Bot added a commit to jdx/mise-action that referenced this pull request Oct 6, 2026
<!-- entire-trail-link-start -->
https://entire.io/gh/jdx/mise-action/trails/37
<!-- entire-trail-link-end -->

This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [jdx/renovate-config](https://redirect.github.com/jdx/renovate-config)
| workflow | patch | `v1.0.1` → `v1.0.2` |

---

### Release Notes

<details>
<summary>jdx/renovate-config (jdx/renovate-config)</summary>

###
[`v1.0.2`](https://redirect.github.com/jdx/renovate-config/releases/tag/v1.0.2):
: Lockfile workflows recover when mise.lock is stale

[Compare
Source](https://redirect.github.com/jdx/renovate-config/compare/v1.0.1...v1.0.2)

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](https://redirect.github.com/jdx/usage/issues/1520)
(aube 2.6.0 → 2.6.1), this broke both workflows.
([#&#8203;34](https://redirect.github.com/jdx/renovate-config/issues/34),
[@&#8203;jdx](https://redirect.github.com/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.
([#&#8203;33](https://redirect.github.com/jdx/renovate-config/issues/33),
[@&#8203;jdx](https://redirect.github.com/jdx))

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

</details>

---

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

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/jdx/mise-action).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xMzQuMSIsInVwZGF0ZWRJblZlciI6IjQ0LjEzNC4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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