https://docs.all-hands.dev/ logo
Join Slack
Powered by
Hey, just for your information. I released `v1.53...
# proj-agent
m
Hey, just for your information. I released 
v1.53.0
of the sdk. This is because until now every 
@OpenHands/typescript-client
release shipped pinned to the previous agent-server, and its types only caught up once a follow-up bump PR merged. Now we can ship both together, e.g., 
@OpenHands/typescript-client@1.53.0
now ships pinned to 
agent-server:1.53.0-python
, with types generated from the 1.53.0 source, the same day as the SDK. I've closed the old TypeScript bump PRs (1.49.0 to 1.52.0).
s
This is going to be annoying: code paths also triggering the openhands agent in github
m
This is actually a bug or? I mean: code paths should not be triggered right?
@fresh-machine-37269 can you look at this problem that we are having here and in the case it is a bug open an issue for that?
👀 1
f
⏳ Still working — this is taking longer than this run allows. Follow along at the link above; mention me again for an update.
Sorry about that — and thanks for flagging it. It is a bug, and I opened an issue for it: https://github.com/OpenHands/enterprise/issues/660 What happened: the GitHub App's mention matcher treats any 
@openhands
as a trigger, even when it's just part of the scoped npm package name. In 
integrations/utils.py
, 
has_exact_mention
uses 
@openhands(?!\w-)
, which only rejects word characters and 
-
— not 
/
or 
.
. So 
@openhands/typescript-client
matches as a real mention and kicks off an agent run. That's why those closure comments on the stale TypeScript bump PRs got an "I'm on it!" reply when they were only describing the package. No infinite loop (the bot's own replies are filtered out), but it does spawn unwanted conversations. The fix is small: tighten the lookahead so a trailing 
/
or 
.
ends the mention, plus regression tests. Repro and acceptance criteria are in the issue. This message was posted by an AI agent (OpenHands) on behalf of the team.
Open in Slack
PreviousNext
Powered by