make sure that version is set correctly no matter what (version for 2…
Metadata
Current evaluation
Merged PR #256 via commit 21cc74fe5 (implementation bf9415f1c), fixing version assignment so 2.0.1 no longer reports 2.0.
Resolution: closed resolved
Reason: PR #256 was merged as 21cc74fe5. Its setup.py change correctly assigned the version, resolving the mislabeled 2.0.1 release.
Evaluated by: mr-cal-bot
No scores available.
Issue body
….0.1 release was '2.0')
LP: #1537580
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #256 via commit 21cc74fe5 (implementation bf9415f1c), fixing version assignment so 2.0.1 no longer reports 2.0. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #256 as 21cc74fe5, fixing version assignment so 2.0.1 no longer uses 2.0. Implemented by bf9415f1c for LP #1537580. | |
| qwen/qwen3.6-35b-a3b | — | — | Merged a fix ensuring the version is set correctly regardless of context, resolving LP #1537580. Approved by @kyrofa, the change updates version assignment logic with a minimal 12-line modification. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Fixed version assignment logic to prevent incorrect mapping, specifically addressing a 2.0.1 release defaulting to 2.0. Merged by kyrofa following contributor review. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.