feat(cli): add minimum release age flag to lock and ls-remote

[risu729]

Summary

Adds --before support to two more commands that need date-aware version discovery:

• mise ls-remote --before <date> filters remote version listings by release timestamp.
• mise lock --before <date> resolves fuzzy/latest tool requests against versions released before the cutoff before writing or previewing lockfile entries.
• Both commands honor all three cutoff sources: the CLI flag, per-tool install_before, and global [settings] install_before, with the CLI flag taking precedence.

This is intended to support potential mise integration work in Renovate, where tooling may need to list and lock versions using a release-date cutoff.

Implementation Notes

ls-remote still fetches the normal cached full remote version metadata and applies the effective date filter after reading it. That keeps the cache independent of the requested cutoff and avoids caching a filtered result for one cutoff that could incorrectly affect a later query with a different cutoff.

lock builds the toolset with a ResolveOptions.before_date override when the flag is present, while preserving the existing per-tool and global install_before fallback behavior when it is not.

Tests

• mise run test:e2e e2e/cli/test_ls_remote e2e/cli/test_lock
• cargo fmt --check

[gemini-code-assist]

Code Review

This pull request introduces a --before flag to the mise lock and mise ls-remote commands, allowing users to filter tool versions based on their release date. The changes include updates to the CLI argument parsing, logic for resolving toolsets with date constraints, and new E2E tests to verify the functionality. Feedback suggests making the before field public in the Lock struct for consistency and optimizing the lock command to use the cached toolset when no date filter is applied to avoid unnecessary overhead.

[greptile-apps]

Greptile Summary

This PR extends the existing --minimum-release-age / install_before date-cutoff mechanism to two more commands: mise ls-remote and mise lock. Both commands respect the same three-tier precedence (CLI flag → per-tool install_before → global [settings] install_before), and the lock path correctly bypasses installed-version fast paths when a cutoff is active so that date-aware resolution reaches the remote version metadata.

• ls-remote applies the resolved per-backend cutoff after fetching the full cached version list, keeping the cache cutoff-independent.
• lock rebuilds the toolset with the CLI cutoff when provided and resolves overridden latest requests through the async resolution path; tool_version.rs gains should_filter_installed_versions guards to prevent offline-only fallbacks from bypassing the cutoff.

Confidence Score: 5/5

Safe to merge; the changes are well-tested end-to-end and additive, with no impact on existing behaviour when the new flag is absent.

The core logic is consistent with the existing resolve_before_date first-wins precedence already in use elsewhere, and the new code paths are guarded by before_date.is_some() so they are entirely inert when the flag is not supplied. The offline/prefer-offline guard in tool_version.rs correctly restricts the installed-version bypass to online resolution only, and a dedicated regression test covers that path.

No files require special attention.

Important Files Changed

Filename	Overview
src/cli/lock.rs	Adds --minimum-release-age to lock; builds a fresh toolset with before_date when CLI flag is present, and applies per-tool date merging in get_tools_to_lock via ToolRequest::resolve_options; async refactor of get_tools_to_lock is non-trivial
src/cli/ls_remote.rs	Adds --minimum-release-age (alias --before) to ls-remote; resolves the effective date per-backend via resolve_before_date_for_backend and filters output through VersionInfo::filter_by_date; --before alias is hidden (not visible in --help)
src/install_before.rs	Adds resolve_before_date_for_backend helper that resolves effective date cutoff for a specific backend, short-circuiting to CLI date when set; consistent with the existing first-wins precedence of resolve_before_date
src/toolset/tool_version.rs	Adds should_filter_installed_versions guard to skip installed-version fast paths when a before_date cutoff is active and not in offline/prefer-offline mode; also adds the same guard for the npm-semver range path
src/toolset/tool_request.rs	Adds resolve_options method that merges per-tool minimum_release_age with the base ResolveOptions using the existing first-wins precedence logic
e2e/cli/test_lock	Comprehensive new e2e tests covering global settings, per-tool overrides, CLI flag precedence, installed-version bypassing, lockfile-scope scoping, and relative durations
e2e/cli/test_ls_remote	New e2e tests for --minimum-release-age on ls-remote covering global, per-tool, and CLI-override cutoff sources; also verifies that cached full version list is not affected by filtered queries
e2e/cli/test_install_prefer_offline_no_refresh	Adds regression test confirming that a configured date cutoff does not break installed-version fallback in prefer-offline/offline mode
src/backend/mod.rs	Minor comment updates replacing --before flag references with generic "release-date filter/cutoff" wording

_{Reviews (24): Last reviewed commit: "[autofix.ci] apply automated fixes" | Re-trigger Greptile}

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[risu729]

Blocking: I need to make the scope of mise lock clear.