release: 0.6.1 — contact email change + ship CF citation fixes to PyPI#2
Conversation
Contact email changed to dcm.anonimizer@gmail.com across the project author metadata (pyproject.toml -> visible on the PyPI page), SECURITY.md, the early-access issue template, the GitHub Pages landing (docs/index.html mailto links + early-access CTA), and a new Contact section in the README so it renders on the PyPI project page. Replaces the prior plusultra.dev@proton.me. Version bumped 0.6.0 -> 0.6.1 so the artifact published to PyPI matches its git tag (main had already advanced past v0.6.0 with the CF citation fixes; a republished 0.6.0 would not match the v0.6.0 tag, and the compliance manifest embeds tool_version, so provenance must stay exact). 0.6.1 is byte-for-byte behaviourally identical to 0.6.0 on the de-identification pipeline; it ships the CF-18/CF-17/CF-14 compliance-citation corrections plus this email change. CHANGELOG 0.6.1 section added; landing-page version banner bumped (keeps test_version_coherence green). Full suite 226 passed, ruff + mypy --strict clean, twine check PASSED on the 0.6.1 sdist + wheel.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: db61dc4bc7
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| Questions, bug reports, security disclosures, or hosted-service / early-access | ||
| enquiries: email **dcm.anonimizer@gmail.com** or open a | ||
| [GitHub issue](https://github.com/Ces107/dcm-anon/issues). |
There was a problem hiding this comment.
Because this sentence groups “security disclosures” with ordinary bug reports and then offers a public GitHub issue as an alternative, users can be steered into disclosing vulnerabilities publicly. This contradicts the responsible-disclosure path in SECURITY.md lines 52-54, which limits security reports to email or GitHub Security Advisories; split security disclosures out so they do not inherit the public issue option.
Useful? React with 👍 / 👎.
1 participant
Release 0.6.1: contact-email change + ships the CF-18/CF-17/CF-14 compliance-citation fixes to PyPI.
Contact email
Changed
plusultra.dev@proton.me->dcm.anonimizer@gmail.comacross:pyproject.tomlauthor email (this is what shows on the PyPI project page)README.md(renders on the PyPI page)SECURITY.md, the early-access issue templatedocs/index.htmlGitHub Pages landing (mailto links + early-access CTA)Version bump 0.6.0 -> 0.6.1
mainhad already advanced past thev0.6.0tag (CF citation fixes), and now this email change. Re-publishing "0.6.0" to PyPI would produce an artifact that does not match its git tag — unacceptable for a compliance tool whose manifest embedstool_version. So this ships as 0.6.1: behaviourally identical to 0.6.0 on the de-identification pipeline, carrying the CF-18/CF-17/CF-14 corrections + the email change.Verification
Full suite 226 passed, ruff + mypy --strict clean,
twine checkPASSED on the 0.6.1 sdist + wheel,test_version_coherencegreen (landing-page banner bumped).After merge: tag
v0.6.1, publish to PyPI (first 0.6.x on PyPI; 0.5.0 currently live), GitHub release.