[Task] Resolve release/version metadata mismatch: source project versions report 0.1.3, while module manifests still report 0.1.2; focused checks fail until these are reconc... #2

Closed
opened 2026-07-06 11:26:42 +02:00 by zemion · 1 comment
Owner

Imported from the consolidated GovOPlaN product backlog.

  • Source: /mnt/DATA/Nextcloud/ADD ideas UG/Products/govoplan/backlog.md
  • Line: 53
  • Section: Inbox

Imported backlog item:

- [ ] Resolve release/version metadata mismatch: source project versions report `0.1.3`, while module manifests still report `0.1.2`; focused checks fail until these are reconciled.
<!-- codex-backlog-fingerprint:c492c70692998e509d5b67e8 --> Imported from the consolidated GovOPlaN product backlog. - Source: `/mnt/DATA/Nextcloud/ADD ideas UG/Products/govoplan/backlog.md` - Line: `53` - Section: `Inbox` Imported backlog item: ```markdown - [ ] Resolve release/version metadata mismatch: source project versions report `0.1.3`, while module manifests still report `0.1.2`; focused checks fail until these are reconciled. ```
zemion added this to the Inbox milestone 2026-07-06 12:56:32 +02:00
Author
Owner

Codex status: done.

Completed evidence:

  • Python package versions, WebUI package versions, and module manifest versions now align at 0.1.6 for the installable GovOPlaN package set.
  • requirements-release.txt now pins backend module git dependencies to v0.1.6, matching webui/package.release.json.
  • docs/RELEASE_DEPENDENCIES.md now shows v0.1.6 in the release dependency table and release-tag example.

Verification:

  • metadata scan over GovOPlaN package/WebUI manifests excluding the currently out-of-scope files repo -> no mismatches outside govoplan-web website versioning
  • rg -n "0\.1\.2|0\.1\.3|v0\.1\.4" requirements-release.txt webui/package.release.json docs/RELEASE_DEPENDENCIES.md -> no matches
  • ./.venv/bin/python -m unittest tests.test_access_contracts tests.test_module_system -> 66 tests OK

Closing because the original manifest/source version mismatch has been reconciled and the release pins now match the current tag.

Codex status: done. Completed evidence: - Python package versions, WebUI package versions, and module manifest versions now align at `0.1.6` for the installable GovOPlaN package set. - `requirements-release.txt` now pins backend module git dependencies to `v0.1.6`, matching `webui/package.release.json`. - `docs/RELEASE_DEPENDENCIES.md` now shows `v0.1.6` in the release dependency table and release-tag example. Verification: - metadata scan over GovOPlaN package/WebUI manifests excluding the currently out-of-scope files repo -> no mismatches outside `govoplan-web` website versioning - `rg -n "0\.1\.2|0\.1\.3|v0\.1\.4" requirements-release.txt webui/package.release.json docs/RELEASE_DEPENDENCIES.md` -> no matches - `./.venv/bin/python -m unittest tests.test_access_contracts tests.test_module_system` -> 66 tests OK Closing because the original manifest/source version mismatch has been reconciled and the release pins now match the current tag.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: add-ideas/govoplan-core#2
No description provided.