Bump version to 0.3.11 and update changelog - #834
Merged
Conversation
PyPI is still on 0.3.10; the v0.3.11 GitHub Release created earlier never actually published, since docs/conf.py's release string (which setup.py uses as the package version) was never bumped, so the build collided with the already-published 0.3.10 and twine rejected it. Also backfills CHANGELOG.md with the batch of issue-triage fixes from PRs QData#830-QData#832 (bug fixes across AttackedText, GreedyWordSwapWIR, Augmenter, HuggingFaceModelWrapper, Attack device placement, and validators, plus the Trainer padding fix and train --dataset-from-file addition), which had landed on master without a changelog entry. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Adds entries for QData#786, QData#797, QData#804, QData#810, QData#813, QData#817, QData#818, QData#819, QData#822 - the batch of community PRs merged into master since 0.3.10 that predate this session's work but had no CHANGELOG.md entries either. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/conf.py'sreleasestring from0.3.10to0.3.11— this is whatsetup.pyuses as the actual PyPI package version.CHANGELOG.mdwith the batch of issue-triage fixes from Fix bert-attack slowness, CLARE <SPLIT>-token corruption, and WordSwapInflections POS mismatch #830, Fix six more issues from the unresolved-bugs backlog #831, and Fix training padding, add train --dataset-from-file, close doc gaps #832, which landed on master without changelog entries.Why
PyPI is still on
0.3.10. Av0.3.11GitHub Release already exists (created back in April) and did trigger the publish workflow, but that run failed — almost certainly becausedocs/conf.py's version string was never bumped for it, so the build still produced0.3.10, which PyPI rejects as a duplicate upload.This PR only bumps the version number and changelog — it does not create a new GitHub Release or trigger a publish. Once this merges, a maintainer can create a
v0.3.11GitHub Release (or delete/recreate the existing stale one) to actually publish to PyPI.Test plan
docs.conf.releaseresolves to0.3.11, consumed correctly bysetup.pygrep -rn "0.3.10"across.py/.cfg/.toml/.rst)black --check docs/conf.pyclean🤖 Generated with Claude Code