#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 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!
3 replies
hi @user , I've resolved it manually
Thanks @user Balashov! Heads up though — I'm still hitting “Interactions on this repository have been restricted to prior contributors only” when I try to open the PR, and
thejoshuasilverstone-cloud doesn't show up in EXTERNAL_CONTRIBUTORS.md on main yet. #4590 is still open too. Anything else I should do, or is there another step in flight?✅1
@user I've merged it