chore(deps): bump band-sdk from 1.4.2 to 3.0.0 in /docker/band_python_kit/echo-agent - #599
Conversation
Bumps [band-sdk](https://github.com/band-ai/band-sdk-python) from 1.4.2 to 3.0.0. - [Release notes](https://github.com/band-ai/band-sdk-python/releases) - [Changelog](https://github.com/band-ai/band-sdk-python/blob/main/CHANGELOG.md) - [Commits](band-sdk-v1.4.2...band-sdk-v3.0.0) --- updated-dependencies: - dependency-name: band-sdk dependency-version: 3.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
amit-gazal-band
left a comment
There was a problem hiding this comment.
✅ Approved by the dependabot-triage skill.
Validated in a consolidated batch run alongside #529 (pydantic-settings). uv sync resolves the echo-agent starter's own lock, main.py imports and constructs EchoAdapter cleanly against the new band-sdk major, and tests/docker/test_echo_agent.py still passes. No automated harness in this repo builds/runs this starter workspace's own lock inside a container end-to-end (the docker_build live test builds the base image from the root project's lock, not this one), so this was verified by direct import/construction rather than a live agent turn.
Bumps band-sdk from 1.4.2 to 3.0.0.
Release notes
Sourced from band-sdk's releases.
... (truncated)
Changelog
Sourced from band-sdk's changelog.
... (truncated)
Commits
08a61c9chore: release main (#580)547615achore(band-mcp): pin next release to 2.1.0 (#581)342a538ci: revert split release PRs, prune dead release-please config (#579)3d2b446ci: split release-please PRs per package (#576)1227061feat: add agent-scoped memory support (#575)9bad9e5fix: integrate band-sdk-core event validation into band-sdk-python (#574)eb2a404feat: add file transfer capability to the Python SDK (INT-1261) (#573)e005fabfix: flush the ACP collecting client at turn end in codex-acp e2e tests (#571)df379a6fix: bound e2e health-check curls with --max-time (#570)fc62742fix: stabilize Codex thought smoke (#567)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)