You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
When a new release is published, users visiting the Jan website may not immediately see the latest build version available for download. This can cause confusion and prevent users from accessing the most recent features or bug fixes.
Steps to reproduce:
Observe the Jan website/download section
Publish a new release with a higher version number than the currently published version.
Wait for a few minutes (less than 10 minutes) after the release has been published.
Access the Jan website as an anonymous user.
Navigate to the download section.
Observe that the latest build version available for download is not the newly published version, but rather the previous version.
Expected behavior:
When a new release is published, the Jan website should immediately update the latest build version available for download.
Users visiting the download page should see the newly published version as the latest version available for download.
Notes:
This issue may be caused by a delay in the synchronization of the build version information between the build system and the website.
The root cause of this issue may be related to the API or the synchronization mechanism used between the build system and the website.
This issue can be reproduced consistently by publishing a new release and observing the download page on the Jan website.
Screenshots
Additional context
Currently, we have to make modifications to temporally bypass the issue each release manually
The text was updated successfully, but these errors were encountered:
Description:
When a new release is published, users visiting the Jan website may not immediately see the latest build version available for download. This can cause confusion and prevent users from accessing the most recent features or bug fixes.
Steps to reproduce:
Expected behavior:
Notes:
Screenshots
Additional context
Currently, we have to make modifications to temporally bypass the issue each release manually
The text was updated successfully, but these errors were encountered: