d8f81cbdf1
Fixes #6391. The issue here was quite nuanced: where we merged a PR, and then merged the changes into an earlier PR, but left it open, the earlier PR could end up getting the release information comment from keyman-server instead of the later, merged PR. This was because the commit would appear in both PRs, so GitHub would report on both of them. This is not a 100% fix -- but it should stop the PR tagging on unmerged pull requests. The one situation where this may leave a gap is where we have multiple PRs merged on the same day, where a later PR's changes are merged into an earlier PR; in this case I think it is possible that one of the PRs will not get the informative version comment. But given the current fix should avoid the more common situation, I am comfortable to leave it as is for now. This is only informative data... and a more complete fix is a distraction. |
||
|---|---|---|
| .. | ||
| history | ||
| l10n | ||
| version | ||
| build-download-resources.sh | ||
| build-utils.sh | ||
| github.inc.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