Skip to content

AttackLM v0.13.0 — Docs sync with attacklm-dataset audit-bugfixes

Latest
Latest

Choose a tag to compare

View all tags
@Veedubin Veedubin released this 11 Jul 07:00
· 18 commits to main since this release
v0.13.0
da6cfe9

AttackLM v0.13.0 — Docs sync with attacklm-dataset audit-bugfixes

Docs-only release. No code change. No PyPI publish (v0.12.3 remains the latest on PyPI).

The upstream attacklm-dataset repo shipped 5 audit-harness bug fixes in v0.4.1 and 2 docs commits in v0.4.2. This AttackLM release is the docs sync — the AttackLM CLI flag set is unchanged; the fixes are in the implementation under the hood.

Changes (docs only)

  • README.md audit table: "MIA reference attack (loss + zlib)" → "MIA reference attack (loss on assistant turn + zlib entropy)" with a one-line explanation of the upstream fix.
  • README.md test count badge: 368+ → 504+ (was stale from a prior session).
  • README.md test count in testing section: 18 → 24 test files.
  • README.md added "Note on the audit harness" subsection in the Verify block, pointing readers to the attacklm-dataset CHANGELOG and README for the underlying bug details.
  • CHANGELOG.md new [Unreleased] — 2026-07-10 entry pointing at the upstream fixes.
  • __version__ bumped from 0.12.3 → 0.13.0 for introspection correctness.

Why no PyPI publish?

v0.13.0 is docs-only. Publishing a docs-only bump to PyPI would force every pip install --upgrade attacklm to download a wheel with the same code as v0.12.3. The PyPI tag will stay at v0.12.3 until the next functional change (probably v0.14.0 with the LiRA training pipeline or a similar feature).

Install

pip install "attacklm[all]==0.12.3"   # PyPI stable (unchanged)
# or for the docs sync:
git clone https://github.com/Veedubin/AttackLM.git
cd AttackLM
git checkout v0.13.0
pip install -e ".[all]"

Verify

$ python -c "import attacklm; print(attacklm.__version__)"
0.13.0
$ attacklm --help
# shows the same CLI as v0.12.3 (no new flags; docs only)
$ pytest tests/ -q
# 504+ passed (was 368+ before; the discrepancy is the test sweep
# from the prior session that didn't get a version bump)

Related

Assets 3
Loading