Start the harness package at 0.1.0 - #14
Conversation
|
Claude finished @euyis1019's task in 24s —— View job No bugs or security issues found. The diff is three version-string substitutions ( |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Automated Claude review completed. Review run: https://github.com/lexmount/Lexbench-Headless-Browser/actions/runs/32216195452. Please check Claude's inline feedback and summary comment for details.
The package version arrived at 0.5.0 in the first commit, with no 0.1 through 0.4 behind it and no record of what the 5 stood for. Sitting next to a corpus labelled v0_4, it read as the next step in that sequence, which it never was: one number counts corpus generations, the other counts releases of this code. 0.1.0 says what is true, that this is the first public cut of the harness, and no longer invites the comparison. Both manifests and the two root entries in the lockfile move together; dependency versions and the license are untouched.
c0f8490 to
439dd9b
Compare
|
Claude finished @euyis1019's task in 18s —— View job No bugs or security issues found. The diff is three version-string substitutions ( |
There was a problem hiding this comment.
Automated Claude review completed. Review run: https://github.com/lexmount/Lexbench-Headless-Browser/actions/runs/32217766830. Please check Claude's inline feedback and summary comment for details.
1 participant
The package version was
0.5.0from the repository's first commit, with no 0.1 through 0.4 behind it and nothing on record for what the 5 meant. Next to a corpus labelledv0_4, it read as the next step in that sequence. It never was:v0_4counts corpus generations (there arefixtures/v0_2,v0_3,v0_4directories andv2_/v4_task prefixes to match), while this number counts releases of the harness code.0.1.0is the first public cut of the harness, which is what this is, and it no longer invites the comparison.package.json,pyproject.tomland the two root entries ofpackage-lock.jsonmove together; dependency versions are untouched andnpm ls --package-lock-onlystill reports the lockfile consistent. Nothing reads this value at runtime:run_manifest.jsonrecords adapter and tree digests rather than a harness version, andinstalled_pip_versionlooks up driver packages, not this one.A version field cannot be dropped altogether. PEP 621 requires
versionunless the project declares it dynamic, and removing it frompackage.jsonwhile the lockfile still carries one makesnpm cicomplain.