We ❤️ MCP
Especially @caarlos0. He fixed a handful of MCP related bugs in this release. Now the question is what is he doing with MCP?
Thanks also to @neomantra, @BrunoKrugel , and Crush all-star @Amolith for crushin’ some other bugs.
Thanks for using Crush and see you soon! 💘
Changelog
Fixed
- 8c9ce8e: fix: close binding in user cmd dialog (#1221) (@Amolith)
- 69be8c2: fix(bedrock): detect credentials set by
aws configure(#1232) (@andreynering) - 1a40fba: fix(grep): check mime type (#1228) (@caarlos0)
- 23e0fd4: fix(mcp): add type assertion guards (#1239) (@neomantra)
- ce72a48: fix(mcp): append to os.Environ() (#1242) (@caarlos0)
- b896a25: fix(mcp): avoid nil errors for tool parameters (#1245) (@BrunoKrugel)
- 3a99542: fix(mcp): improve STDIO error handling (#1244) (@caarlos0)
- 4b1001c: fix(tui): paste on arguments input (#1240) (@caarlos0)
Other stuff
- 05457d5: refactor: use clamp from /x/exp/ordered (#1236) (@meowgorithm)
Verifying the artifacts
First, download the checksums.txt file, for example, with wget:
wget 'https://github.com/charmbracelet/crush/releases/download/v0.11.2/checksums.txt'Then, verify it using cosign:
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' \
--cert 'https://github.com/charmbracelet/crush/releases/download/v0.11.2/checksums.txt.pem' \
--signature 'https://github.com/charmbracelet/crush/releases/download/v0.11.2/checksums.txt.sig' \
./checksums.txtIf the output is Verified OK, you can safely use it to verify the checksums of other artifacts you downloaded from the release using sha256sum:
sha256sum --ignore-missing -c checksums.txtDone! You artifacts are now verified!
Thoughts? Questions? We love hearing from you. Feel free to reach out on X, Discord, Slack, The Fediverse, Bluesky.