View Issue Details

This bug affects 1 person(s).
 2
IDProjectCategoryView StatusLast Update
20262Bug reportsOtherpublic2025-09-12 11:11
Reportermig5 Assigned Toc_schmitz  
PrioritynoneSeverityminor 
Status closedResolutionno change required 
Product Version6.6.x 
Summary20262: Git tags and releases seem out of sync at Github
Description

Hi,

I previously reported this on the Forum at https://forums.limesurvey.org/forum/development/157548-git-tags-and-releases-seem-out-of-sync-at-github but was recommended to file a bug report.

I noticed that whenever someone publishes a new release on Github, the corresponding 'tag' that is made at exactly the same timestamp at github.com/LimeSurvey/LimeSurvey/tags , is the preceding release.

In other words, the 'tagged' official releases published on Github are always exactly one release behind what you just committed to master branch.

Is this expected? It feels like a logic error in a script, given the timestamps are basically identical between 'tag new release / publish the previous release tag'. If not, can it be fixed so that the 'tagged' releases are caught up with the official release being made?

Steps To Reproduce

N/A

TagsNo tags attached.
Bug heat2
Complete LimeSurvey version number (& build)N/A
I will donate to the project if issue is resolvedNo
Browser
Database type & versionN/A
Server OS (if known)
Webserver software & version (if known)
PHP VersionN/A

Users monitoring this issue

There are no users monitoring this issue.

Activities

c_schmitz

c_schmitz

2025-09-12 11:11

administrator   ~83400

This is intendend. We do not want people to download the 'latest' release from Github using the tag, because the version from Github is missing the build number, which is crucial for certain services like ComfortUpdate.
Instead the latest version should always be downloaded from https://community.limesurvey.org/downloads/ .

Issue History

Date Modified Username Field Change
2025-09-11 23:29 mig5 New Issue
2025-09-12 11:11 c_schmitz Assigned To => c_schmitz
2025-09-12 11:11 c_schmitz Status new => closed
2025-09-12 11:11 c_schmitz Resolution open => no change required
2025-09-12 11:11 c_schmitz Note Added: 83400
2025-09-12 11:11 c_schmitz Bug heat 0 => 2