GitStream incorrectly flags current date as a future date

[echarrod]

Describe the bug

GitStream incorrectly identifies the current date 2026-02-04 as a "future date" and suggests changing it to 2024-02-04. The date is correct — today is 2026-02-04.

The suggestion from GitStream:

🪲 Bug - Future Date: Update all instances of "2026-02-04" to the correct current date (likely 2024 or 2025).

To Reproduce

Steps to reproduce the behavior:

1. Run Docker version of GitStream on GitLab
2. Add a file containing today's date (2026-02-04) in a merge request
3. Create MR
4. GitStream comments suggesting the date is incorrect and should be 2024-02-04

Expected behavior

• GitStream should recognize 2026-02-04 as the current date and not flag it as a future date

Screenshots

The suggested change incorrectly replaces 2026-02-04 with 2024-02-04:

- **Created**: 2026-02-04
+ **Created**: 2024-02-04

Additional context

• Running gitStream Docker image version: v1.0.188
• It appears GitStream's internal date awareness may be outdated, causing it to believe the current year is 2024 or 2025

[vim-zz]

Thank you, looking at it. Btw you can also use /gs feedback and send us the issue directly

[echarrod]

Ah nice, didn't know about that. So we can reply to the thread in our private Gitlab with /gs feedback and leave feedback there?

[vim-zz]

Oh, my bad, it's still not supported in GitLab. I hope we get there soon