Skip to content

Release activeagent 1.3.0 - #366

Merged
TonsOfFun merged 1 commit into
mainfrom
release/activeagent-1.3.0
Aug 19, 2026
Merged

Release activeagent 1.3.0#366
TonsOfFun merged 1 commit into
mainfrom
release/activeagent-1.3.0

Conversation

@TonsOfFun

Copy link
Copy Markdown
Contributor

Why

activeagent is still published at 1.2.0 while actionagent has shipped 1.2.1 and 1.2.2. Two changes have sat on main unreleased since, and one is a bug that makes the dashboard misreport every streamed run.

on main published
agent-as-tool delegation (#360)
streaming token usage (#362)

Verified by unpacking the published gem: record_stream_usage is absent from activeagent-1.2.0, and lib/active_agent/delegation/ does not exist in it.

Why minor, not patch

Delegation adds a public DSL (delegation :action, description:) and a new lib/active_agent/delegation/ tree. Shipping a new core primitive under a patch version hides it from anyone reading the changelog to decide whether to upgrade.

The bug this unblocks

A stream: true generation reports zero tokens and zero cost, and the context-pressure estimate that depends on them never renders. On a self-hosted dashboard that means an empty Tokens column and $0.00 beside runs that plainly called the API.

Confirmed end to end against OpenRouter (anthropic/claude-sonnet-4.5): a streamed probe went from usage=nil to input=14 output=4, matching the same prompt issued non-streaming, and a real 30-page document-enrichment batch went from 0/0 to 475/72.

The v1.2.0 tag

The tag had drifted to 094ebe79 (#364) — later than the commit actually published as the 1.2.0 gem — so git diff v1.2.0..main showed nothing outstanding when in fact two changes were. It is repointed here to 147418c8, verified byte-identical to the published gem across lib/active_agent.rb, base.rb and _base_provider.rb.

⚠️ The tag move must be pushed with git push --force origin v1.2.0, and anyone who fetched it in the meantime needs git fetch --tags --force.

Compatibility

actionagent's >= 1.2, < 2 constraint already accepts 1.3.0, so no coordinated bump is needed.

Checklist before merging

  • CI green
  • git push --force origin v1.2.0 (tag repoint)
  • Tag v1.3.0 after merge
  • Confirm the release workflow publishes both gems in dependency order

🤖 Generated with Claude Code

Two changes have sat unreleased on main since 1.2.0 was published, and one of
them is a bug that makes the dashboard misreport every streamed run.

Minor rather than patch: agent-as-tool delegation adds a public DSL
(`delegation :action, description:`) and a new lib/active_agent/delegation/
tree. Shipping a new primitive under a patch version would hide it from
anyone reading the changelog to decide whether to upgrade.

The streaming token fix rides along. Without it a `stream: true` generation
reports zero tokens and zero cost, and the context-pressure estimate that
depends on them never renders — a self-hosted dashboard shows an empty
Tokens column beside runs that plainly called the API.

actionagent needs no coordinated bump: its `>= 1.2, < 2` constraint already
accepts this.

Also repoints the v1.2.0 tag, which had drifted to a commit later than the
one published as the 1.2.0 gem, so `git diff v1.2.0..main` overstated what
was released.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@TonsOfFun
TonsOfFun marked this pull request as ready for review August 19, 2026 03:24
@TonsOfFun
TonsOfFun merged commit a548fb3 into main Aug 19, 2026
7 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant