Skip to content

terminal-bench-2@1.0, and each dataset numbers its own versions from 1.0 - #19

Merged
rzonyx merged 1 commit into
mainfrom
terminal-bench-2
Oct 24, 2026
Merged

rzonyx merged 1 commit into
mainfrom
terminal-bench-2

Conversation

@rzonyx

@rzonyx rzonyx commented Oct 24, 2026

Copy link
Copy Markdown
Contributor
  • CONTRIBUTING: a dataset's version is ours and starts at 1.0. A new upstream release bumps the first component (1.0 → 2.0); a change of ours bumps the last (1.0 → 1.0.1).
  • terminal-bench-2@1.0 has 2.0.1's tasks, byte for byte. superseded.yaml maps terminal-bench@2.0 and @2.0.1 to it.
  • New environment.mirror: the images stay in hbench-envs/terminal-bench, so nothing is mirrored again.
  • dataset_index.py leaves a superseded version out only once its successor is in the index. terminal-bench stays listed until terminal-bench-2@1.0 is published.
  • After merge: run Publish for terminal-bench-2 1.0. It runs Index at the end.
  • Conflicts with README in hbench's sections; maintainer steps in docs/PUBLISHING.md #14 in README and CONTRIBUTING.

Tests: 356 OK (5 new) and validate_sources.py, run locally.

A dataset's version is now this repository's own, starting at 1.0: a new
upstream release or commit bumps the first component, a change of ours
the last. Upstream's 2.0 names Terminal-Bench 2 rather than a revision of
it, so the dataset becomes terminal-bench-2@1.0, with 2.0.1's tasks byte
for byte, and superseded.yaml maps both terminal-bench versions to it.

Its images stay in hbench-envs/terminal-bench: environment.mirror names
the package when it is not the dataset's name, so nothing is mirrored
again and no task byte changes.

dataset_index.py leaves a superseded version out only once its successor
is in the index, so terminal-bench stays listed until terminal-bench-2@1.0
is published.
@rzonyx
rzonyx merged commit a35482e into main Oct 24, 2026
45 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant