Skip to content

BioRouter v1.75.2

Choose a tag to compare

View all tags
@Broccolito Broccolito released this 13 May 05:53
v1.75.2
979332a

BioRouter v1.75.2 Release Notes

Release Date: May 2026
Repository: github.com/BaranziniLab/BioRouter

A small, focused patch release. Headline fix: a fresh install of Versa API Bedrock with nothing but an Access Key ID and Secret Access Key now works on the first try — the UCSF MuleSoft Bedrock proxy endpoint, region, and credentials are wired in explicitly so the AWS SDK no longer falls through to ~/.aws/credentials or env-var profiles.

Downloads

Platform File Install
macOS (Apple Silicon) BioRouter-1.75.2-arm64.dmg Open the DMG and drag BioRouter.app to /Applications
macOS (Intel) BioRouter-1.75.2-x64.dmg Open the DMG and drag BioRouter.app to /Applications
Windows (x64) BioRouter-win32-x64-1.75.2.zip Unzip and run BioRouter.exe
Linux Ubuntu / Pop!_OS (x64) biorouter_1.75.2_amd64.deb sudo dpkg -i biorouter_1.75.2_amd64.deb
Linux Fedora / RHEL (x64) BioRouter-1.75.2-1.x86_64.rpm sudo rpm -i BioRouter-1.75.2-1.x86_64.rpm

What's Fixed

Versa API Bedrock — works out of the box on a fresh machine

Previously, a brand-new install of Versa API Bedrock would fail with a signing or 403 error even when the user had entered a valid UCSF-issued Access Key ID and Secret Access Key. Two problems:

  1. The UCSF MuleSoft Bedrock proxy URL (https://unified-api.ucsf.edu/general/awsai) was not exposed as a configurable field — it only worked if the user happened to have it in their config.yaml. A fresh install silently hit public AWS Bedrock instead of the UCSF proxy, where UCSF-issued keys aren't recognized.
  2. The frontend pre-populated AWS_PROFILE='default'. When the user had no ~/.aws/credentials file, the AWS SDK's profile-resolution step interfered with the env-var-credential fallback in subtle ways.

Both fixed:

  • AWS_ENDPOINT_URL_BEDROCK is now a first-class config key on the Versa Bedrock provider, pre-populated with the UCSF proxy URL and editable from the Settings UI.
  • The Rust provider now constructs an explicit Credentials object from VERSA_BEDROCK_ACCESS_KEY_ID + VERSA_BEDROCK_SECRET_ACCESS_KEY and injects it directly into the AWS SDK config. The default credential chain (profile files, IMDS, env vars) is bypassed entirely.
  • Region and endpoint URL are always pinned on the SDK loader (us-west-2 and the UCSF proxy URL by default).
  • The misleading AWS_PROFILE default was removed from the Versa Bedrock setup form.

Net effect: a user who has nothing but the access key + secret in BioRouter — no ~/.aws/, no env vars, no AWS CLI configuration — gets a working Versa Bedrock setup on the first try.

Provider helper text — UCSF-specific language removed from generic providers

The plain Amazon Bedrock and Azure OpenAI provider cards now describe only the generic provider behavior:

  • Azure OpenAI: "Models through Azure OpenAI Service (uses Azure credential chain by default)."
  • Amazon Bedrock: "Run models through Amazon Bedrock."

UCSF-specific instructions live under the Versa API Azure and Versa API Bedrock cards, which is where they belong.

Extension updater + uv sync — augmented PATH and clearer errors

uv sync calls from the extension installer and updater now run with the augmented PATH (~/.cargo/bin, ~/.local/bin, /usr/local/bin, plus the Windows uv install dir) instead of a half-built per-call PATH. When the call fails, the error message now surfaces the real failure (process error, stderr, stdout, or exit code) instead of an empty uv sync failed: line.

Upgrading

No manual migration needed. Replace your existing installation with the new package for your platform.

  • macOS: open the new DMG and drag BioRouter.app into /Applications, replacing the existing app
  • Linux: install the new .deb or .rpm over the existing installation (dpkg -i and rpm -U handle upgrades automatically)
  • Windows: unzip and replace the existing installation folder

Existing Versa Bedrock users do not need to change their config — the new code reads the same AWS_ENDPOINT_URL_BEDROCK key if you already had it set, and falls back to the UCSF proxy default if you didn't.

Changes Since v1.75.1

  • fix(versa-bedrock): bypass AWS default credential chain, pin UCSF endpoint + region
  • fix(providers): drop UCSF wording from generic Azure OpenAI and Amazon Bedrock helper text
  • fix(extension-updater): share augmented PATH with uv sync, report real error detail
  • chore(release): bump to 1.75.2

UCSF BioRouter is developed by the Baranzini Lab at the University of California, San Francisco.

Assets 7
Loading