Repository navigation
docs(version): align README/setup/CHANGELOG with reality - #36
Merged
Merged
Conversation
The CHANGELOG has a [2.2.0] section dated 2026-07-25 describing completed Phase C desktop UX work (PR-09, PR-10). The setup.py declares version '2.2.0' and src/__init__.py declares __version__ = '2.2.0'. The README references 'v2.2.0' as a released feature. However, NO v2.2.0 git tag exists. The latest released tag is v2.1.0. Per ecosystem policy (do not invent tags; reduce claims instead of exaggerating), this PR aligns docs with reality: - setup.py: '2.2.0' -> '2.2.0.dev0' (PEP 440 pre-release marker) - src/__init__.py: __version__ '2.2.0' -> '2.2.0.dev0' (with comment) - CHANGELOG.md: '[2.2.0] — 2026-07-25' -> '[Unreleased] — 2.2.0-dev' with a clear note that the work is on main but not tagged yet - README.md: 'جديد في v2.2.0' -> 'جديد (غير مُصدَّر بعد — Unreleased)' with a note pointing to the release checklist The actual code is unchanged. Only version metadata + docs. To release v2.2.0: 1. Complete docs/RELEASE_CHECKLIST_v2.2.0.md 2. Bump '2.2.0.dev0' -> '2.2.0' in setup.py + src/__init__.py 3. Convert CHANGELOG '[Unreleased]' -> '[2.2.0] — <date>' 4. git tag v2.2.0 5. git push origin v2.2.0
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.
What changed
setup.py:2.2.0→2.2.0.dev0(PEP 440 pre-release marker + explanatory comment)src/__init__.py:__version__2.2.0→2.2.0.dev0(with comment)CHANGELOG.md:[2.2.0] — 2026-07-25→[Unreleased] — 2.2.0-dev(with note that work is on main but not tagged)README.md:جديد في v2.2.0→جديد (غير مُصدَّر بعد — Unreleased)(points to release checklist)Why it matters
The CHANGELOG
[2.2.0]section describes completed Phase C desktop UX work (PR-09, PR-10) andsetup.pydeclared version2.2.0, but nov2.2.0git tag exists. Latest released tag isv2.1.0. Per ecosystem policy (do not invent tags; reduce claims instead of exaggerating), this PR aligns docs with reality.Reference:
ECOSYSTEM_STATE.mdinrepo-sync-toolkit(PR #1).Risks / intentionally not changed
v2.2.0tag (that requires completingdocs/RELEASE_CHECKLIST_v2.2.0.mdfirst).src/core/smart_tagger.py(medical scope tracked in separate PR).mobile/orbuildozer.spec(separate quarantine PR).Verification performed
setup.py+src/__init__.py.git diff --stat: 4 files, 17 insertions, 5 deletions.git tag -l: onlyv2.1.0exists.Blockers / manual follow-up
None. After merge, to release v2.2.0:
docs/RELEASE_CHECKLIST_v2.2.0.md2.2.0.dev0→2.2.0insetup.py+src/__init__.py[Unreleased]→[2.2.0] — <date>git tag v2.2.0 && git push origin v2.2.0Next PR
PR #3 — intellifile-mobile-quarantine-or-decision.