#747 allow version metadata for each release

[John Romano D'Orazio]

I just started using sourceforge yesterday, and upon uploading a release for my package, I was surprised to find that I can only create project metadata (title, description, etc.). I would have expected to be able to indicate a version number for an uploaded release. So that if I want to automate a check for latest release from the software itself, let's say using the JSON endpoint https://sourceforge.net/projects/bibleget/best_release.json , it would be possible to compare the version number associated with the current release. That way if the version number is greater than the currently installed version, we can automate an update mechanism. Is there no way of associating a version number with a release file?

[Dillon Walls]

Hi,

We do not currently support setting version metadata for specific files. However, what many users do is create folders for each release (e.g. "/1.0.0/setup.exe") or add version numbers to their filenames (e.g. "setup-1.0.0.exe").

Using either of those strategies, you should be able to accomplish what you would like to do by fetching best_release.json and parsing out the version number from the file name/path.

Sincerely,
SourceForge Support