docs(igp24): version the release as v1.1.0 and document tags

#7
by sairdata - opened
SAIR Foundation org
•
edited 24 days ago

Prepare the repository to be tagged v1.1.0. v1.0.0 stays where it is, so that tag keeps pointing to the same files.

  • README: the version line and the citation (text and BibTeX note) say v1.1.0 instead of the ambiguous v1.
  • README: add a short Versions section. It lists what each tag contains, says tags are never moved, shows how to pin revision="v1.1.0", and explains why the docs/dataset-layout branch is kept (the v1.0.0 README examples resolve it).
  • SHA256SUMS: update the README.md hash. No other entry changes.

Checks before opening: every SHA256SUMS entry matches the actual file hashes at main (85 files) and at v1.0.0 (74 files). Compared with v1.0.0, main only adds files and changes README.md and SHA256SUMS. No data file was modified.

Not included: a full structural audit over all 50,428,828 records has not been run. reports/dataset-audit.json remains the labelled sampled audit, with all shard checksums recomputed.

After merging: create tag v1.1.0 on the merge commit.

Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com

🤖 Generated with Claude Code

sairdata changed pull request status to merged

Sign up or log in to comment