[jdx]

Summary

• remove the registry test command for jc so release-branch registry CI skips it
• leave the existing aqua:kellyjonbrazil/jc and pipx:jc backends unchanged

Context

jc@1.25.7 currently fails registry CI with a checksum mismatch for jc-1.25.7-linux-x86_64.tar.gz. GitHub now reports the asset digest as sha256:5b7ab595bfbaa70f07a15136bbc3c09d6dbf65891248bf1f060ec3da29608a2c, while CI expected sha256:e7b4bd9eca4164276b99b39cc56e2dbc9536ad7b997f80a70ea9b7778f5fded4. The release was published on 2026-06-18, but that Linux asset was updated on 2026-06-29.

Testing

• git diff --check

---

Note

Low Risk
Registry-only change that disables one tool’s CI smoke test; no runtime or install-backend behavior changes.

Overview
Removes the test entry from registry/jc.toml so registry CI no longer runs jc --version against {{version}} for this tool.

aqua:kellyjonbrazil/jc and pipx:jc backends and the tool description are unchanged; only post-install verification is skipped to avoid failing CI after the upstream jc@1.25.7 Linux tarball checksum changed post-release.

^{Reviewed by Cursor Bugbot for commit cff6925. Bugbot is set up for automated code reviews on this repo. Configure here.}

Summary by CodeRabbit

• Chores
  • Simplified configuration by removing an unused test entry, leaving only the active backend and description settings.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

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

Review profile: CHILL

Plan: Pro Plus

Run ID: 2a4d1c34-ee55-4785-a5ad-cebf20973777

📥 Commits

Reviewing files that changed from the base of the PR and between 57cae0f and cff6925.

📒 Files selected for processing (1)

• registry/jc.toml

💤 Files with no reviewable changes (1)

• registry/jc.toml

---

📝 Walkthrough

Walkthrough

The test configuration block was removed from registry/jc.toml, which previously defined a jc --version command and its expected output for verification purposes.

Changes

jc Registry Configuration

Layer / File(s)	Summary
Remove test block registry/jc.toml	Removed the test entry defining a jc --version command and expected output, leaving only backends and description.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Poem

A little block hopped out today,
No more version checks in its way,
Just backends and words remain in sight,
A rabbit's nibble, clean and light. 🐇

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the main change: disabling the jc registry test configuration.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

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

[greptile-apps]

Greptile Summary

Removes the test entry from registry/jc.toml to prevent release-branch registry CI from failing due to a checksum mismatch on the jc-1.25.7-linux-x86_64.tar.gz asset (the asset was republished on 2026-06-29 with a different digest). Both backends (aqua:kellyjonbrazil/jc and pipx:jc) are left untouched.

• Deletes one line: the test = { cmd = "jc --version", expected = "jc version: {{version}}" } entry, so CI no longer tries to install and verify the broken jc release.
• No other configuration is altered; this is purely a CI-stability workaround until the upstream checksum issue is resolved.

Confidence Score: 5/5

Safe to merge — the only change is removing a test stanza that causes CI failures; backends and all other configuration are unchanged.

The deletion is minimal and targeted, only affecting CI test execution for jc. Both aqua and pipx backends remain configured, so users can still install jc normally. The motivation (upstream asset republished with a new digest) is clearly documented in the PR description.

No files require special attention. Consider re-adding the test stanza once the upstream jc checksum stabilizes.

Important Files Changed

Filename	Overview
registry/jc.toml	Removes the test stanza to skip CI validation for jc while leaving both backends intact; straightforward workaround for a checksum mismatch on jc@1.25.7.

_{Reviews (1): Last reviewed commit: "registry: disable jc test" | Re-trigger Greptile}

[github-actions]

Hyperfine Performance

mise x -- echo

Command	Mean [ms]	Min [ms]	Max [ms]	Relative
mise-2026.6.14 x -- echo	21.6 ± 0.9	19.7	25.8	1.00
mise x -- echo	22.5 ± 1.3	20.3	38.6	1.04 ± 0.07

mise env

Command	Mean [ms]	Min [ms]	Max [ms]	Relative
mise-2026.6.14 env	21.5 ± 1.0	19.5	26.2	1.00
mise env	22.3 ± 0.9	19.9	26.5	1.04 ± 0.06

mise hook-env

Command	Mean [ms]	Min [ms]	Max [ms]	Relative
mise-2026.6.14 hook-env	22.3 ± 0.9	20.3	26.4	1.00
mise hook-env	23.2 ± 1.0	20.9	28.9	1.04 ± 0.06

mise ls

Command	Mean [ms]	Min [ms]	Max [ms]	Relative
mise-2026.6.14 ls	18.8 ± 0.8	16.7	22.3	1.00
mise ls	19.5 ± 0.9	17.4	24.6	1.04 ± 0.07

xtasks/test/perf

Command	mise-2026.6.14	mise	Variance
install (cached)	150ms	150ms	+0%
ls (cached)	67ms	70ms	-4%
bin-paths (cached)	73ms	74ms	-1%
task-ls (cached)	142ms	143ms	+0%