Skip to content

Leave terminal-bench@2.0 out of the dataset index - #18

Merged
rzonyx merged 1 commit into
mainfrom
index-skips-superseded
Oct 23, 2026
Merged

rzonyx merged 1 commit into
mainfrom
index-skips-superseded

Conversation

@rzonyx

@rzonyx rzonyx commented Oct 23, 2026

Copy link
Copy Markdown
Contributor

hbench datasets list shows terminal-bench@2.0 and @2.0.1 with nearly the same description and no hint which to use. 2.0.1 is 2.0's tasks with each image pinned by digest to its mirror.

  • New superseded.yaml (terminal-bench@2.0: terminal-bench@2.0.1); dataset_index.py leaves out every version it maps and says so in its log.
  • Nothing is deleted: GHCR keeps serving 2.0 to jobs that name it.
  • README examples use 2.0.1; CONTRIBUTING says where a superseded version goes.
  • After merge, run the Index workflow so the published index drops 2.0.
  • Touches the README's dataset table and examples, as README in hbench's sections; maintainer steps in docs/PUBLISHING.md #14 does.

Tests: unit tests (351 OK, 1 new) and validate_sources.py, locally.

terminal-bench@2.0.1 is 2.0's tasks with each environment image pinned
by digest to its mirror, but hbench datasets list showed both with
nearly the same description and no hint which to use. superseded.yaml
now maps 2.0 to 2.0.1, and dataset_index.py leaves out any version it
maps, so the list and the interactive run offer 2.0.1 only. The
registry keeps serving 2.0 to jobs that name it. The README's examples
use 2.0.1.
@rzonyx
rzonyx merged commit 6fe4f1e into main Oct 23, 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