v0.73.0

charmbracelet/crushv0.73.0May 26, 2026by github-actions[bot]

AI Summary

This release adds AWS Bedrock Europe support with a separate provider using eu-west-1 region, complementing the existing Bedrock US provider in us-east-1. This allows European users to use models in their preferred region due to employer restrictions or preferences.

Key Highlights

Added AWS Bedrock Europe provider (eu-west-1)
Bedrock US now explicitly uses us-east-1
Improved model changed notification UI

New Features

AWS Bedrock Europe support with separate provider for European region

Full Release Notes

# Follow-up to Bedrock

Last Friday, we shipped some changes for Bedrock to make it work by default for most users.

Before that release, your `AWS_REGION` or `AWS_DEFAULT_REGION` could instruct Crush to try to reach Bedrock at a different region, and it could not work at all because most models are only available in very few regions. Because it was not clear why Crush was not working for Bedrock, this could be confusing to users. We then enforced `us-east-1` for region because that one should work for everyone.

## Bedrock Europe 🇪🇺 

Since then, a few of you reached out telling us that models are also available on `eu-west-1`, and some users in Europe might prefer or need (due to employer restrictions) to use an European region.

Starting on this release, you'll see two providers if you search for "bedrock":

* Bedrock US: will use `us-east-1`
* Bedrock Europe: will use `eu-west-1`

<img width="679" height="447" alt="Screenshot 2026-05-26 at 14 45 31" src="https://github.com/user-attachments/assets/c6447ef7-3913-42e4-9758-bcc2bcd2d1cd" />

That's all for today.
Stay tuned for the next releases!

## Changelog
### New!
* ae20f1f65175e4b1c2b9bbfc3f9b556a1589b7ec: feat: add aws bedrock europe (#3016) (@andreynering)
### Fixed
* 1db7629b199a8950078caf14f924b07e6460f7dd: fix(ui): improve model changed notification (#3015) (@andreynering)

---

<details>
<summary>Verifying the artifacts</summary>

First, download the [`checksums.txt` file](https://github.com/charmbracelet/crush/releases/download/v0.73.0/checksums.txt) and the [`checksums.txt.sigstore.json` file](https://github.com/charmbracelet/crush/releases/download/v0.73.0/checksums.txt.sigstore.json) files, for example, with `wget`:

```bash
wget 'https://github.com/charmbracelet/crush/releases/download/v0.73.0/checksums.txt'
wget 'https://github.com/charmbracelet/crush/releases/download/v0.73.0/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).