Skip to content

Conversation

@Unshure
Copy link
Member

@Unshure Unshure commented Jul 2, 2025

Description

Sync latest v0.1.x changes to v0.1.x branch

Related Issues

N/A

Documentation PR

N/A

Type of Change

Other (please describe): Sync changes

Testing

How have you tested the change? Verify that the changes do not break functionality or introduce warnings in consuming repositories: agents-docs, agents-tools, agents-cli

  • I ran hatch run prepare

Checklist

  • I have read the CONTRIBUTING document
  • I have added any necessary tests that prove my fix is effective or my feature works
  • I have updated the documentation accordingly
  • I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
  • My changes generate no new warnings
  • Any dependent changes have been merged and published

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

awsarron and others added 30 commits July 2, 2025 18:11
* feat: Add non-streaming support to BedrockModel

* fix: Add more test coverage

* fix: Update with pr comments
…nds-agents#55)

* Added hyphen to allowed characters in tool name validation
…ig (strands-agents#86)

* fix(telemetry): correct environment variable precedence for OTEL configuration

* fix(telemetry): update get_tracer function to adapt the changes

* fix(telemetry): fix tracer initialization

---------

Co-authored-by: Jack Yuan <jackypc@amazon.com>
* feat: Deploy to pypi on release

* feat: get version from tag
Co-authored-by: Sourabh Sarupria <rob.sarupria@mac.chi.chicorp>
Co-authored-by: Sourabh Sarupria <rob.sarupria@e5865.x.akamaiedge.net>
* Update pr-and-push.yml

* Update pypi-publish-on-release.yml
* Preserve deeply nested schemas

* Refactor schema tests to assert entire structure

---------

Authored-by: Luke Harris <lkhar@amazon.com>
…gents#180)

See open-telemetry/opentelemetry-python#4615 but it looks like an OpenTelemetrySDK update caused type errors

---------

Co-authored-by: Mackenzie Zastrow <zastrowm@users.noreply.github.com>
Co-authored-by: Mrityunjay Shukla <mrshukla@amazon.com>
To avoid the code owners from being added to every PR

Co-authored-by: Mackenzie Zastrow <zastrowm@users.noreply.github.com>
…strands-agents#178)

Enable direct method tool invocations of `example_tool` to match tools with the name of `example-tool`, which fixes strands-agents#139. In the case where no direct match is found but multiple tools would match, we throw an error to avoid ambiguous errors

Co-authored-by: Mackenzie Zastrow <zastrowm@users.noreply.github.com>
…gents#193)

Per follow-up to strands-agents#178, where we discussed preventing similar_tool and similar-tool from both being added to the tool registry, to avoid ambiguity in direct-method invocations
poshinchen and others added 19 commits July 2, 2025 18:11
* build(a2a): add a2a deps and mitigate otel conflict
* Use deployment environment gating for integration tests.

* Only run on PRs that target main.

* Use correct head name.
Having the dependency breaks uv installs as swagger-parser depends on pre-release library which is not allowed by default

As far as I can tell, this dependency is not used anywhere and can be safely removed

Co-authored-by: Mackenzie Zastrow <zastrowm@users.noreply.github.com>
…nts#223)

current_delay was being thrown away and not applied to subsequent retries

Co-authored-by: Mackenzie Zastrow <zastrowm@users.noreply.github.com>
…nts#221)

- Add a single script that runs the commands we want contributions to run.
 - Revamp the contribution template by:
    - Using HTML comments to guide the author, reducing the need to delete the text
    - Converting the type of change to be a flat list, allowing authors to delete all except the one they want
    - Updated the checklist items to allow items that are unnecessary to still be checked

Co-authored-by: Mackenzie Zastrow <zastrowm@users.noreply.github.com>
While reading the through the event loop, it made more sense to me to inline the implementation - most of the actual apis are signature + docs, while the actual code is 2 lines each.

Co-authored-by: Mackenzie Zastrow <zastrowm@users.noreply.github.com>
…ents#60)

* feat: add structured output support using Pydantic models

- Add  method to Agent class for handling structured outputs
- Create structured_output.py utility for converting Pydantic models to tool specs
- Improve error handling when extracting model_id from configuration
- Add integration tests to validate structured output functionality

* fix: import cleanups and unused vars

* feat: wip adding `structured_output` methods

* feat: wip added structured output to bedrock and anthropic

* feat: litellm structured output and some integ tests

* feat: all structured outputs working, tbd llama api

* feat: updated docstring

* fix: otel ci dep issue

* fix: remove unnecessary changes and comments

* feat: basic test WIP

* feat: better test coverage

* fix: remove unused fixture

* fix: resolve some comments

* fix: inline basemodel classes

* feat: update litellm, add checks

* fix: autoformatting issue

* feat: resolves comments

* fix: ollama skip tests, pyproject whitespace diffs
…nds-agents#254)

Related to strands-agents#238

Co-authored-by: Mackenzie Zastrow <zastrowm@users.noreply.github.com>
…ands-agents#258)

Right now when you decorate a function you get back another function that mimics the behavior of a python module. Going forward, we're discussing adding helper/utility methods for AgentTool and in anticipatation of those changes return an AgentTool implementation that also acts like the original function.

Co-authored-by: Mackenzie Zastrow <zastrowm@users.noreply.github.com>
@Unshure Unshure requested a review from a team as a code owner July 2, 2025 18:13
@Unshure
Copy link
Member Author

Unshure commented Jul 2, 2025

Chose a different approach where we are making the this target branch a historic branch, and renaming it to v0.1.5. Then we will properly set up a new v0.1.x branch with the correct git history.

@Unshure Unshure closed this Jul 2, 2025
@Unshure Unshure deleted the v0.1.x branch September 25, 2025 01:00
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.