Eberhard Beilharz 4d81589f48 maint(common): use unique names for Keyman version variables ... Previously the builder scripts defined a readonly `VERSION` environment variable for the Keyman version. That caused problems when another (external) script tried to define a `VERSION` variable. We encountered this problem when trying to move the TC build steps of a configuration into a single script (#13399) when we tried to source `~/.nvm/nvm.sh`. This change uses a Keyman specific prefix for the version variables and renames `VERSION` → `KEYMAN_VERSION` etc. Unfortunately these variables are used in a lot of places, so this turned out to be a bit of a yak shave. Test-bot: skip		2025-05-07 18:46:51 +02:00
..
src	maint(common): use unique names for Keyman version variables	2025-05-07 18:46:51 +02:00
test	chore(developer): rename test files	2024-11-28 14:32:09 +01:00
.gitignore	chore(developer): move server with no changes	2022-05-23 12:15:34 +10:00
build-addins.inc.sh	chore(developer): upgrade node-gyp to support Python 3.12+	2024-08-12 06:08:52 +07:00
build.sh	chore(developer): use JQ variable in script	2025-01-20 14:11:42 +07:00
package.json	chore(deps): bump express from 4.19.2 to 4.20.0	2024-09-11 07:18:39 +00:00
tsconfig.json	Revert "chore(developer): remove redundant references from tsconfig.json"	2024-08-01 08:57:27 +10:00