Starts to resolve the chaos of putting version numbers into every package.json file. Adds a new keyman-version package which mimics the version information in build-utils.sh. This will eventually replace resources/web-environment. Fixes the build for the lexical model compiler tools to remove refs to package.json version and use keyman-version instead. More fixes coming in a follow-up. |
||
|---|---|---|
| .. | ||
| history | ||
| l10n | ||
| version | ||
| build-download-resources.sh | ||
| build-utils.sh | ||
| help-keyman-com.sh | ||
| htm-link.lua | ||
| html-link.lua | ||
| increment-version.sh | ||
| jq-license.txt | ||
| jq-win64.exe | ||
| jq.inc.sh | ||
| offline-help-style-spec.txt | ||
| README.md | ||
| report-history.sh | ||
| run-required-test-builds.sh | ||
| sentry-control.inc.sh | ||
| trigger-builds.inc.sh | ||
| trigger-definitions.inc.sh | ||
| vswhere-LICENSE.txt | ||
| vswhere.exe | ||
| xcode-utils.sh | ||
Release builds
A release is triggered nightly whenever a pull request has been merged to the branch; it
runs from a TeamCity build configuration that runs increment-version.sh and then uploads
the resulting HISTORY.md to https://downloads.keyman.com/history/HISTORY.md.
To manually make a release (for example if a build falls over for a transient error or there was a build configuration problem), create a new PR that targets the branch, merge it, and then run the Trigger Release Builds build configuration for that branch. If you have no changes, see that as an opportunity to improve documentation, including this file...
Various tools
vswhere
vswhere.exe is used by Keyman Core to select a Visual Studio version on Windows.
Official source: https://github.com/microsoft/vswhere. License: MIT
jq-win64
jq-win64.exe is used by various builds for json query.
Official source: https://stedolan.github.io/jq/. License