#general
New release! 🚀🚀🚀
1.2.40 (2026-05-12)
Miscellaneous Chores
---
This PR was generated with Release Please. See documentation.
Just found a small bug that when we add the api key of llm, we have to write name of key, even though the field itself shows optional.
it can be good first issue
cc: @user
Hi team — working on bounty #4468 (Anthropic Workload Identity Federation). CLA is signed and my PR is ready, but my contributor-onboard PR archestra-ai/archestra#4590 got a merge conflict on EXTERNAL_CONTRIBUTORS.md right after it opened. The merge-external-contributors workflow only triggers on PR open, so it's stuck. Could a maintainer rebase or reopen it so I get added to the allowlist? Then I can submit the WIF PR (already committed and tested locally). Thanks!
Hi community, Diego Aguirre here, Nice to meet you all. Looking forward to connect with others interested in AI and contribute with the community. 👋
New release! 🚀🚀🚀
1.2.44 (2026-05-12)
Bug Fixes
---
This PR was generated with Release Please. See documentation.
Read-only live mirror of Archestra.AI Slack
👋Join the discussion withAI enthusiasts!Hi community, Diego Aguirre here, Nice to meet you all. Looking forward to connect with others interested in AI and contribute with the community. 👋
6 replies
Team, I saw this https://github.com/archestra-ai/archestra/issues/4416
Is this issue refearing to Google Agent 2 Agent protocol?
I was wonderig If I could make my first contribution to the community if this is about a2a protocol, since I've created about 3 / 4 projects with this protocol. Not interested in the bounty honestly, just interested in getting started and make a contribution to the community.
cc: @user @user ❤️
Welcome!
The issue looks good, and kindly asking not to tag team members without a specific need
Thank you Matvey, I will do, can I be assigned to that issue or I can attempt to solve it? I see Ildar Ishhkadov has it assigned.