Skip to content

chore(main): release 0.6.0 - #20

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--modelmux
Open

chore(main): release 0.6.0#20
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--modelmux

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.6.0 (2026-07-29)

Features

  • upstreams: impose reasoning depth per-upstream, and carry reasoning back (a3bdbe7)
  • upstreams: minMaxTokens — a RAISE-ONLY floor for the outbound token cap (66399b9)

Bug Fixes

  • cli: report the version and fail on an unrecognised command (46fa645)
  • rules: an authorization fact is repo-local and dated — it never travels (36854ce)
  • rules: the harness outranks this kit on whether to dispatch at all (0554372)
  • upstreams: passthrough must never substitute a metered key for a subscription (39c5adc)

This PR was generated with Release Please. See documentation.

@github-actions github-actions Bot changed the title chore(main): release 0.5.2 chore(main): release 0.6.0 Jul 29, 2026
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--modelmux branch from 718dfca to 6149afd Compare July 29, 2026 07:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants