The old v0.1 header contains a malformed version date string.
Current header
# Version: 0.1 - 2025-10-2025
Why this matters
This is only a cosmetic issue, but version metadata should still be clean and unambiguous.
Bad header metadata becomes annoying later when comparing files, preparing releases, or writing patch notes.
Fix approach
Correct the date to the intended format, for example:
# Version: 0.1 - 2025-10-25
Status
Still open as a metadata cleanup item unless corrected during the next commit.
### Problem
The old v0.1 header contains a malformed version date string.
### Current header
```python
# Version: 0.1 - 2025-10-2025
```
### Why this matters
This is only a cosmetic issue, but version metadata should still be clean and unambiguous.
Bad header metadata becomes annoying later when comparing files, preparing releases, or writing patch notes.
### Fix approach
Correct the date to the intended format, for example:
```python
# Version: 0.1 - 2025-10-25
```
### Status
Still open as a metadata cleanup item unless corrected during the next commit.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
The old v0.1 header contains a malformed version date string.
Current header
Why this matters
This is only a cosmetic issue, but version metadata should still be clean and unambiguous.
Bad header metadata becomes annoying later when comparing files, preparing releases, or writing patch notes.
Fix approach
Correct the date to the intended format, for example:
Status
Still open as a metadata cleanup item unless corrected during the next commit.
Version string in header has malformed dateto [Task]: Version string in header has malformed date