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
..
api-verification.yml	maint(common): use unique names for Keyman version variables	2025-05-07 18:46:51 +02:00
auto-merge-keyman-server-pr.yml	chore(common): Specify Keyman repo on GitHub actions	2023-12-11 10:24:30 +07:00
close-linked-issues-for-merged-prs.yml	chore: use sha instead of version for security	2025-02-27 17:40:51 +01:00
crowdin.yml	chore(common): Update dependencies in crowdin GitHub action	2025-04-28 16:42:49 +07:00
deb-packaging.README.md	chore(linux): rename "Debian packaging" to "Ubuntu packaging"	2025-03-17 17:52:18 +01:00
deb-packaging.yml	maint(common): use unique names for Keyman version variables	2025-05-07 18:46:51 +02:00
labeler.yml	chore(common): Specify Keyman repo on GitHub actions	2023-12-11 10:24:30 +07:00