release: v0.4.0 - #42
Conversation
…6 + D14) MINOR bump per SemVer (gap= forwarding, TransientGridWarning, SOURCE_DATE_EPOCH are backward-compatible additions). CITATION.cff was still at 0.2.0 (stale since 04-17) -> 0.4.0/2026-06-07. Board note "v0.3.0-Release-Tag" was stale: v0.3.0 tag exists since 05-28. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
![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: 3734b7c7b0
ℹ️ 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".
| - name: "Coworker Research" | ||
| version: "0.2.0" | ||
| date-released: "2026-04-17" | ||
| version: "0.4.0" |
There was a problem hiding this comment.
When citation consumers honor preferred-citation—including the GitHub citation widget referenced in README.md—they will still present the software as v0.2.0 because its title remains unchanged at line 31, even though this release now declares version: "0.4.0". This gives users incorrect version provenance for the new release; update the preferred-citation title or remove its embedded version.
Useful? React with 👍 / 👎.
| Release cut: everything below shipped on `main` between `v0.3.0` (2026-05-28) | ||
| and this tag (18 commits, PRs #34–#41 — audit waves 2026-06-04/06-06 + D14 |
There was a problem hiding this comment.
The new release section says everything below came from 18 commits and PRs #34–#41, but the section also documents changes introduced by earlier PRs such as #28, #31, #32, and #33, while the repository history from the v0.3.0 version-sync commit through the pre-release parent contains only 15 commits. Since this statement is presented as the release audit trail, it gives readers an incorrect scope and should be replaced with the actual commit/PR range.
Useful? React with 👍 / 👎.
1 participant
Summary
Release-Cut v0.3.0 -> v0.4.0:
_version.py0.4.0 (single source, PR#40-Mechanik), CHANGELOG-Schnitt[0.4.0] - 2026-06-07(18 Commits, PRs #34-#41: Audit-Wellen 06-04/06-06, fail-closed-Haertung, dynamic-version P0, D14-Physikskalierung), CITATION.cff 0.2.0(stale)->0.4.0.MINOR statt PATCH:
gap=-Forwarding +TransientGridWarning+SOURCE_DATE_EPOCHsind rueckwaertskompatible API-Zuwaechse (SemVer).Test plan
pytest -qlokal: 214 passed / 1 skipped, Exit 0 (nach editable-Reinstall;test_version_single_source= PR#40-Drift-Guard fing die stale Metadata erwartungsgemaess)liouscope.__version__== 0.4.0 (Import-Beleg)Nach Merge: Tag
v0.4.0+ GitHub-Release (Notes aus CHANGELOG) + KANON-Nachzug.