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
From this commit it appears that the version number is currently stored in three different places:
BlocklyPropClient.py
about.txt
package/blocklypropclient-installer.iss
and with the recent enhancement of the Mac build/sign/packaging spec and scripts, it is also necessary for it to be placed in the Info.plist's CFBundleShortVersionString element (currently done automatically at signing/packaging time).
Until/unless we have a way to manage this better in the future, I think I should add a small sed script to the repo that will adjust the version in each of the necessary places in one step- something we can use like this, for example:
$ set_version 0.5.3
Do you agree with all of this, above?
The text was updated successfully, but these errors were encountered:
It looks like PR#74 includes a script that tags a number of files with a specific version number. I'm looking at this from an automated build process. Which file tracks the current version number?
@zfi - Not sure I understand the question. If you're asking which file an automated build process should check for an "official" version number, I'd say it's BlocklyPropClient.py.
@zfi
From this commit it appears that the version number is currently stored in three different places:
and with the recent enhancement of the Mac build/sign/packaging spec and scripts, it is also necessary for it to be placed in the Info.plist's CFBundleShortVersionString element (currently done automatically at signing/packaging time).
Until/unless we have a way to manage this better in the future, I think I should add a small sed script to the repo that will adjust the version in each of the necessary places in one step- something we can use like this, for example:
Do you agree with all of this, above?
The text was updated successfully, but these errors were encountered: