Notes on preparing history files

Use GitHub version comparisons to see exact set of changes for each release, for example, the following links determines which changes landed in 11.0.1308.0. Then you will need to manually filter the commit log for pull requests that are merged (e.g. the commit message will say Merge pull request #...), and filter those again by visual inspection for the relevant platform:

https://github.com/keymanapp/keyman/compare/windows-release-beta-11.0.1307.0...windows-release-beta-11.0.1308.0

See also https://teamcity-support.jetbrains.com/hc/en-us/community/posts/360000016000-TeamCity-missing-git-PR-merge-commits-when-calculating-changes-and-thus-post-build-labelling-

and management/release-report.php (which is currently private but hope to add to repo at some point)

---

Generating release notes for an upcoming version

cd ./resources/build/version
./build.sh
cd ../../../

The command to get a list of changes is

node ./resources/build/version/ report-history -b stable-17.0 -t $GITHUB_TOKEN