v0.62.1
charmbracelet/crushv0.62.1Apr 24, 2026by github-actions[bot]
AI Summary
This is a stability release for Crush (v0.62.1) focused on bug fixes and improvements. The release addresses API key validation for MiniMax, fixes 400 Bad Request errors for Fantasy providers, improves LSP server startup reliability, and adds better logging for request retries.
Key Highlights
- Fixed MiniMax API key validation to accept all valid key formats (not just those starting with 'sk-')
- Fixed 400 Bad Request errors for Fantasy providers by fixing request failure scenarios
- Improved LSP server startup reliability by replacing sticky unavailable cache with retry backoff
- Added structured OnRetry logging for better debugging when requests fail
- Fixed re-authorization flow that wasn't triggering under certain conditions
Full Release Notes
# Stability release Open Source :tm: is all about community, and this release got some nice contributions from our loved users! ## MiniMax fix Crush wasn't allowing users to _some_ MiniMax API keys, but now all keys should work. For context, MiniMax does not have an endpoint to validate API keys. We were checking they at least start with `sk-`, but not all keys from MiniMax have this prefix. Kudos to @flynn-eye for the help with this one! ## Fantasy fix @carsonfarmer made [a contribution](https://github.com/charmbracelet/fantasy/pull/196) to [Fantasy](https://github.com/charmbracelet/fantasy) to fix some scenario where the request could fail. This should fix some 400 Bad Request errors for some providers. ## Tiny fixes @iceymoss, which has been doing some good patches, got two more merged into this release. * LSP servers startup should now be a bit more reliable (#2498) * Better logs when Crush is retrying a request that failed (#2700) Have a great weekend :sparkles: Charm ## Changelog ### Fixed * 549f717263b3fc4520ec1fede5009ddc951db057: fix(agent): implement OnRetry logging with structured retry fields (#2700) (@iceymoss) * e5d95aa79c55b11476d6eb1a5818955844605bdb: fix(hyper): fix re-authorization flow not triggering on certain conditions (#2703) (@andreynering) * f669bd3634215a5e2b3feb8ef7872df0f56d28b8: fix(lsp): replace sticky unavailable cache with retry backoff (#2498) (@iceymoss) * 81daa266819ce8bf4bbb93bb03095116b8de42b4: fix(styles): use semantic names in styles + drop deadcode (@meowgorithm) * 511916ab376490ecd924fd662de1ee0606185b29: fix(ui): logo and grad arguments from earlier refactor (@meowgorithm) * cce8edf9a216337cca46c6457f9ab208c48babd1: fix: remove minimax api key validate (#2688) (@flynn-eye) ### Docs * 28ab548ad2462c659aa4b6325288cae39e3915b0: docs(readme): tiny updates (@andreynering) ### Other stuff * 15f20e6a7acdff8f671ec805671c205addd3dacd: chore(ui): add new letterforms: h, y, p, e, with alts (@meowgorithm) * 4f3a308f708ea53e3b27cb92a02e6515107092ff: chore(ui): formal hypercrush type treatment (@meowgorithm) * 7cbb1dbae2ae8484f72ff627a049d37131bdd4ca: chore(ui): use Lip Gloss for color blends (@meowgorithm) * 31025a1addb9124ceadcc80f346a9e834fcf34a4: chore: auto-update files (@charmcli) --- <details> <summary>Verifying the artifacts</summary> First, download the [`checksums.txt` file](https://github.com/charmbracelet/crush/releases/download/v0.62.1/checksums.txt) and the [`checksums.txt.sigstore.json` file](https://github.com/charmbracelet/crush/releases/download/v0.62.1/checksums.txt.sigstore.json) files, for example, with `wget`: ```bash wget 'https://github.com/charmbracelet/crush/releases/download/v0.62.1/checksums.txt' wget 'https://github.com/charmbracelet/crush/releases/download/v0.62.1/checksums.txt.sigstore.json' ``` Then, verify it using [`cosign`](https://github.com/sigstore/cosign): ```bash cosign verify-blob \ --certificate-identity 'https://github.com/charmbracelet/meta/.github/workflows/goreleaser.yml@refs/heads/main' \ --certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \ --bundle 'checksums.txt.sigstore.json' \ ./checksums.txt ``` If the output is `Verified OK`, you can safely use it to verify the checksums of other artifacts you downloaded from the release using `sha256sum`: ```bash sha256sum --ignore-missing -c checksums.txt ``` Done! You artifacts are now verified! </details> <a href="https://charm.land/"><img alt="The Charm logo" src="https://stuff.charm.sh/charm-banner-next.jpg" width="400"></a> Thoughts? Questions? We love hearing from you. Feel free to reach out on [X](https://x.com/charmcli), [Discord](https://charm.land/discord), [Slack](https://charm.land/slack), [The Fediverse](https://mastodon.social/@charmcli), [Bluesky](https://bsky.app/profile/charm.land).