Considering how fast things are moving and the amount of change, would it make sense to change this line:

to a specific version/tag? I feel like pointing to main may make this a little unstable.

Well, the resolver has 2 modes basically, from this point of view:

• it runs on the latest version <= when it's triggered by the label fix-me or we insert the tag @openhands-agent in a comment
• it runs on main <= when it's triggered by the label fix-me-experimental or we use the tag @openhands-agent-exp in a comment.

So we can choose the stable version, we just have the additional ability to run on main. Livin' on the edge! 😅

Other repos are also able to run on a target branch / main, which uses our main as you pointed out.

(On a side note, that's why we're not sure how to classify these bugs. I do think they're bugs anyway, and they will be in the stable version if we let them (except for the rare case when versioning itself was the problem).

OpenHands started fixing the issue! You can monitor the progress here.

Oops, haha it heard me 😂

What's the difference between the "latest version" and "main"? Does latest version mean latest stable version?

Yes! It's 0.18 now

Oh that's good to know. So when someone copies this : https://github.com/All-Hands-AI/OpenHands/blob/main/openhands/resolver/examples/openhands-resolver.yml

To their repo and they tag "fix-me" or use its name. Does it also use the latest stable version? Or does it use main?

Let's see!

• the labeled issue: [Bug]: Very serious issue! enyst/litellm#4

Looks like it's 0.18.0, if the label is fix-me:

####openhands-ai==0.18.0

Workflow: https://github.com/enyst/litellm/actions/runs/12622492557/job/35170464204#step:4:67

But I'm getting confused. I think it got the workflow file from main, then it executes on 0.18.0... 🤔

Hi @enyst,

I encountered a similar issue and wanted to share my findings. After reviewing the label issue you mentioned, I discovered that the root cause seems to stem from an incorrect installation of OpenHands. This appears to be related to the workflow file, specifically codes around the cat Requirements.txt command. Instead of appending dependencies correctly to the last line, it adds them immediately after the last character in the file.

This behavior causes pip to fail in recognizing the corresponding package, leading to installation issues. For reference, you can check my issue here: #5988. In my case, the Requirements.txt file from my repository was used, and the version characters for openhands_ai were appended incorrectly at the end of the last line, causing the installation to fail.

I hope this helps in identifying and resolving the problem!

OpenHands started fixing the issue! You can monitor the progress here.

A potential fix has been generated and a draft PR #6284 has been created. Please review the changes.