Release activeagent 1.3.1 - #369
Merged
Merged
Conversation
Ships the rendered-user-turn capture (#367) under a version whose tag actually produces it. 1.3.0 was published from a tree that already carried that fix while the PR was still open, so the released gem and the v1.3.0 tag disagree: the tag's source does not reproduce the gem. Anyone auditing the release, or building from the tag, gets a different artifact than the one on rubygems. There is no functional change relative to the published 1.3.0 gem. main is byte-identical to it across lib/, verified file by file. This release exists so the tag, main and the published gem agree again, and upgrading is optional. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Ships #367 under a version whose tag actually produces it.
1.3.0 was published from a tree that already carried #367 while the PR was still open, so the released gem and the
v1.3.0tag disagree — building from the tag yields a different artifact than the one on rubygems.org. Exactly one file differs (lib/active_agent/telemetry/instrumentation.rb); nothing else leaked.v1.3.0main(now #367 is merged)No functional change
mainis now byte-identical to the published 1.3.0 gem acrosslib/, verified file by file. Upgrading from 1.3.0 changes no behaviour. This release exists so the tag,mainand the gem agree again.What #367 fixed, for the changelog record
An agent written the idiomatic way —
instructions:pluslocals:, user message in the action's ERB — passed nomessages:, soprompt.input.messageswas absent from its traces. The system prompt and completion were both captured, which made it easy to miss: the trace looked populated while the half an evaluation scores was missing.Verification
A host app on published
activeagent 1.3.0+actionagent 1.2.2+solid_agent 0.2.0+activeagents-telemetry 0.2.0, no path or git sources:All three attributes (
prompt.input.instructions,prompt.input.messages,llm.output.message) present on every trace, agents auto-registered, tools discovered, tool call captured. The host app's suite: 1232 runs, 4838 assertions, 0 failures.An app-side workaround for the missing user turn was removed from that host and the behaviour held — which is the point: apps should not each have to discover and patch this.
Checklist
v1.3.1after merge🤖 Generated with Claude Code