[GH-ISSUE #1838] 🐛 [Bug] Upgrade notification incorrectly shows version 2.5.2 when running 2.6.0 #719

Closed
opened 2026-02-25 21:35:45 +03:00 by kerem · 3 comments
Owner

Originally created by @IrAlfred on GitHub (Jan 18, 2026).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/1838

Originally assigned to: @mercihabam on GitHub.

The upgrade notification system is displaying incorrect version information. Despite running Cypht version 2.6.0, the notification states "You are currently running Cypht version 2.5.2" and suggests upgrading to version 2.6.0.

Image
Originally created by @IrAlfred on GitHub (Jan 18, 2026). Original GitHub issue: https://github.com/cypht-org/cypht/issues/1838 Originally assigned to: @mercihabam on GitHub. The upgrade notification system is displaying incorrect version information. Despite running Cypht version 2.6.0, the notification states "You are currently running Cypht version 2.5.2" and suggests upgrading to version 2.6.0. <img width="1915" height="817" alt="Image" src="https://github.com/user-attachments/assets/3980de88-a85d-4838-84b4-635280413b69" />
kerem 2026-02-25 21:35:45 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@IrAlfred commented on GitHub (Jan 18, 2026):

Related to https://github.com/cypht-org/cypht/pull/1799

<!-- gh-comment-id:3765721585 --> @IrAlfred commented on GitHub (Jan 18, 2026): Related to https://github.com/cypht-org/cypht/pull/1799
Author
Owner

@IrAlfred commented on GitHub (Jan 19, 2026):

Analysis shows this is not a bug, but a gap in our release process documentation https://github.com/cypht-org/cypht/wiki/How-to-release-Cypht. The issue occurs when don't point to the next version as the 'current' version (see file https://github.com/cypht-org/cypht/blob/master/lib/version.php) prior to release. I'm closing this ticket and update our release documentation to include this necessary step.

<!-- gh-comment-id:3767963579 --> @IrAlfred commented on GitHub (Jan 19, 2026): Analysis shows this is not a bug, but a gap in our release process documentation https://github.com/cypht-org/cypht/wiki/How-to-release-Cypht. The issue occurs when don't point to the next version as the 'current' version (see file https://github.com/cypht-org/cypht/blob/master/lib/version.php) prior to release. I'm closing this ticket and update our release documentation to include this necessary step.
Author
Owner

@mercihabam commented on GitHub (Jan 30, 2026):

I opened: https://github.com/cypht-org/cypht/pull/1849

<!-- gh-comment-id:3824727462 --> @mercihabam commented on GitHub (Jan 30, 2026): I opened: https://github.com/cypht-org/cypht/pull/1849
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/cypht#719
No description provided.