Indeed one could do an update program. One of the reason is the JSON file and there is another reason: there are several BGRABitmap packages which are supposed to have the same version number (regular, for fpGUI and for noGUI).
Though I was hoping some compiler directive like:
const MyPackageVersion={$PACKAGEVERSION};
@lucamar
About updating, I see you mention the JSON update to be separate from the rest. In some way I agree because the proper way is:
- first update packages with the new version (and merge with master branch)
- make a release on the repository with the new version to get the zip file
- update the JSON file with version number and zip file (and merge with master branch)
- package manager is aware of new version
As a matter of fact, I did the latest releases like this:
- update package and JSON file with new version (and merge with master branch)
- hope package manager does not read it in the next seconds
- make a release to get the zip file
I wonder if that could be a problem.