[jdx]

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

Ten http-backed registry tools listed versions without release dates, so minimum_release_age could not hold any of their releases back (#14689). They now report a created_at per version, using the version_date_expr / version_date_url / version_date_next_expr options from #14696 (this PR is stacked on it).

mise ls-remote --json <tool> was checked for each:

Tool	Date source	Undated versions
dart	GCS VERSION object timeCreated, two pages	0 of 180
flutter	release_date in the manifest already used for versions	0 of 195
nomad-pack, sentinel, tfc-agent	HashiCorp releases API timestamp_created, paged 20 at a time	0
nim	build date in each release's nightlies download path on install.html	0 of 41
julia	last-modified in versions.json	104 of 109
android-cli	Date of the apt repo's Release file (never earlier than the build it lists)	0
cursor-agent (also cursor-cli)	the build date every version starts with	0
twg	publishedAt in manifest.json	0

Julia's versions.json only started recording last-modified in August 2026, so releases before that, and prereleases, stay undated; every release since is dated.

Not dateable from what these upstreams publish:

• oc, openshift-install: the mirror's directory index shows no date for version folders (datetime=""), and the release controller and Cincinnati graph carry none. Dating them would take one request per version (about 1,200).
• grok: only https://x.ai/cli/stable (a bare version) is published, and the bucket cannot be listed anonymously.
• muse: the channel document and manifest carry no date.

Old mise clients read the floating registry too; they ignore the new options (checked with 2026.10.11).

Tested with mise run test:e2e cli/test_registry cli/test_registry_floating.

AI-assisted — Tool: Claude Code; model: anthropic/claude-sonnet-5-5; version: claude-code_2-1-299_agent.

🤖 Generated with Claude Code

---

Note

Low Risk
Registry TOML-only metadata; older mise clients ignore the new keys, with behavior limited to version listing and release-age policy.

Overview
Adds version_date_expr (and related version_date_url / version_date_next_expr where needed) to ten HTTP registry tools so remote version listings expose a created_at per release, enabling minimum_release_age for tools that previously had no dates.

Each tool wires upstream-specific metadata: Dart paginates GCS VERSION objects; Flutter reuses manifest release_date; HashiCorp nomad-pack, sentinel, and tfc-agent page the releases API; nim parses nightlies path dates from install.html; julia uses last-modified in versions.json (older/prerelease versions stay blank); android-cli uses the apt Release file date; cursor-agent derives dates from version prefixes; twg reads publishedAt from manifest.json.

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

[coderabbitai]

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 2 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used all 10 included reviews currently available.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

• Configuration used: Repository YAML (base), Central YAML (inherited), Organization UI (inherited)
• Review profile: CHILL
• Plan: Advanced
• Run ID: ded52dd6-c961-4067-a1b5-db1a145da9a5

📥 Commits

Reviewing files that changed from the base of the PR and between 2196f24 and a2c4c1e.

📒 Files selected for processing: 10

• registry/android-cli.toml
• registry/cursor-agent.toml
• registry/dart.toml
• registry/flutter.toml
• registry/julia.toml
• registry/nim.toml
• registry/nomad-pack.toml
• registry/sentinel.toml
• registry/tfc-agent.toml
• registry/twg.toml

• Autofix · 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.}

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge; no actionable issues were established.

Summary

Adds release dates to ten existing HTTP registry entries so minimum_release_age can hold back recent versions.

• Flutter, Julia, and twg versions gain dates from their manifests.
• Cursor Agent and Nim versions gain dates from their build paths.
• Android CLI and Dart versions gain dates from separate release sources.
• HashiCorp tool versions gain dates from their release feeds.

No actionable issues were established. No tests were run during this review.

_{Reviews (4) · Last reviewed commit: "registry: add release dates to http tool..." · Reviewed by Greptile}

[github-actions]

Instruction counts

The comparison never ran — an earlier step failed.

_{a2c4c1e3d4d4 vs `` · measured on the runner, not pushed to the history.}