Skip to content

docs: link rust cache issue #483

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
risu729 wants to merge 1 commit into from
Closed

docs: link rust cache issue #483

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -94,6 +94,11 @@ You can also extend the default cache key:

This gives you full control over cache invalidation based on the specific aspects that matter to your workflow.

### Rust Cache

Rust has a known cache interaction because mise installs Rust through `rustup`.
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot May 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The term "cache interaction" is ambiguous and doesn't clearly convey that caching is partially ineffective for Rust. Using "caching limitation" or "issue" is more descriptive. Additionally, briefly explaining that the cause is the storage location helps users understand the problem immediately without needing to click the link for basic context.

Suggested change
Rust has a known cache interaction because mise installs Rust through `rustup`.
Rust has a known caching limitation because mise installs Rust through `rustup`, which stores data outside the default cache directory.

See [jdx/mise-action#215](https://github.com/jdx/mise-action/issues/215).

## GitHub API Rate Limits

When installing tools hosted on GitHub (like `gh`, `node`, `bun`, etc.), mise needs to make API calls to GitHub's releases API. Without authentication, these calls are subject to GitHub's rate limit of 60 requests per hour, which can cause installation failures.
Expand Down
Loading