chore(release): 2.0.0

[JohnnyWilson16]

Release 2.0.0

Version bump and changelog finalization for the next published release. No code changes — main (e2bfd64, PR #154) is the release content; it has full green CI across all six workflows, including the re-armed T5 benchmark gate.

Version selected: 2.0.0 (from 1.1.1 on PyPI)

• The [Unreleased] changelog section (the July 2026 production-audit remediation, PR Production-audit remediation: safe-by-default cleaning, validator-gated PII, honest release posture #154) changes core cleaning defaults in ways the changelog itself labels breaking: drop_duplicates defaults to off, outlier_action="auto" never rewrites values, dayfirst="auto" never infers column-wide order, fd.anonymize() fails closed, CSV outputs neutralize formula injection by default. SemVer requires a major bump.
• v1.2.0 was tagged (at 9368ea4) but never published to PyPI or GitHub Releases — the July 18 release was stopped on the CleanBench T5 runtime gate. The tag is left untouched (no force-moves); its content ships as part of 2.0.0, and the changelog now says so explicitly.
• PyPI latest is 1.1.1, so users upgrade 1.1.1 → 2.0.0 directly.

Changes in this PR

File	Change
pyproject.toml	version = "2.0.0"
src/freshdata/__init__.py	__version__ = "2.0.0"
CHANGELOG.md	[Unreleased] → [2.0.0] - 2026-07-20 with major-bump rationale; never-published note on [1.2.0]
docs/production-readiness.md	example pin refreshed to freshdata-cleaner==2.0.0

No other version references exist (CITATION.cff's cff-version: 1.2.0 is the CFF format version; README badges are dynamic shields.io).

Validation on the bumped tree

• ruff check . — clean
• mypy src/freshdata — clean (201 files; run with CI's numpy<2.5 pin)
• pytest -m "not online and not large" — 4042 tests selected, 0 failures. Local run exits 1 only on the --cov-fail-under=93 gate (91.97% locally, the known artifact of online/JVM/optional-backend tests skipping outside CI); CI runs the full matrix and enforces this gate authoritatively — it was green on this tree's parent (main@e2bfd64) and re-runs on this PR
• uv build — freshdata_cleaner-2.0.0-py3-none-any.whl (727 KB) + freshdata_cleaner-2.0.0.tar.gz built
• twine check — both artifacts PASSED
• Wheel contents audited: 262 files, all under freshdata/ + dist-info, LICENSE included, no tests/caches/secrets/temp files
• Clean-venv wheel install (py3.12): import OK, __version__/dist metadata = 2.0.0, fd.clean end-to-end with report OK, retained-duplicates default confirmed, CLI entry point OK

Release procedure after merge

Push tag v2.0.0 on the merge commit. release.yml (PyPI Trusted Publishing/OIDC) verifies tag↔version, checks PyPI for collision fail-closed, builds once, twine-checks, smoke-installs, publishes, attests (SLSA + PEP 740), then creates the GitHub Release with artifacts and SHA-256 checksums.

Risks / notes

• The T5 runtime gate stopped the last two release attempts (runner variance vs absolute baseline). It was re-baselined and re-armed in PR Production-audit remediation: safe-by-default cleaning, validator-gated PII, honest release posture #154 and passed on main's tip; a flaky failure on this PR's CI would need one re-run, not a code change.
• No dedicated security scanner (bandit/pip-audit) is configured in the repo; coverage relies on CI's wheel-content guard and the privacy adversarial test suite.
• Dangling v1.2.0 tag remains by design (never force-moved/deleted); documented in the changelog.

🤖 Generated with Claude Code

Summary by CodeRabbit

• New Features
  • Released version 2.0.0 with safer defaults and explicit opt-in for previous behavior.
• Documentation
  • Updated production-readiness guidance to pin version 2.0.0.
  • Clarified release history, including the unpublished 1.2.0 milestone and migration guidance.
• Chores
  • Updated the package version to 2.0.0.

[strix-security]

Strix is installed on this repository, but we couldn't run this PR security review because this workspace's trial has ended. Add a card to resume code reviews here.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: cc543cc4-3ac9-41b2-806f-d0d186864927

📥 Commits

Reviewing files that changed from the base of the PR and between e2bfd64 and bca7a2e.

📒 Files selected for processing (4)

• CHANGELOG.md
• docs/production-readiness.md
• pyproject.toml
• src/freshdata/__init__.py

---

📝 Walkthrough

Walkthrough

The project version is released as 2.0.0 across package metadata and the public version constant. Changelog entries and production-readiness guidance are updated to describe the release and recommend pinning version 2.0.0.

Changes

2.0.0 Release

Layer / File(s)	Summary
Version and release alignment pyproject.toml, src/freshdata/__init__.py, CHANGELOG.md, docs/production-readiness.md	Package metadata, the public version constant, changelog release entries, and the recommended pinned version are updated to 2.0.0.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

• FreshCode-Org/freshdata#109: Updates the same package version sources and changelog release metadata.
• FreshCode-Org/freshdata#150: Updates successive version metadata in the public version constant and changelog.

Suggested reviewers: johnnywilson-portfolio

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is detailed, but it does not follow the required template sections like Description, Type of Change, and Checklist.	Reformat the PR body to match the template and add the missing Description, Fixes #, Type of Change, and Checklist sections.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise and accurately identifies the release version bump and release prep changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/2.0.0-jwd

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

FreshData benchmark report — performance

• freshdata: ?
• python: ?
• platform: ?

fixture	n_rows	n_cols	p50 s	p95 s	peak MB	repair %	false-repair %	preserve %	trust	monotonic	export %

Authored-code reduction (Metric 6)

[JohnnyWilson16]

Post-merge status: tag v2.0.0 was pushed and the release workflow ran, but stopped at the CleanBench T5 runtime gate (+27.68% vs the 20% budget) — nothing was published to PyPI. The failure is deterministic, not runner variance; full analysis, evidence, and the maintainer decision needed to unblock are in #156.