# Keyman Conventional Commit suggestions:
#
# - Link to a Sentry issue with git trailer:
# Fixes: _MODULE_-_ID_
# - Give credit to co-authors:
# Co-authored-by: _Name_ <_email_>
# - Use imperative, present tense ('attach' not 'attaches', 'attached' etc)
# - Don't include a period at the end of the title
# - Always include a blank line before trailers
# - More: https://github.com/keymanapp/keyman/wiki/Pull-Request-and-Commit-workflow-notes
If configuration is set to not automatically downloadupdates
and then from the configuration tab the check for update button is
clicked. If an update is found the upgrade statemachine is now in
state UpdateAvailable. If a updated keyman installer file is then
download direclty from keyman.com. Then installed by running the self
installer then on firstrun the statemachine will still be in the
UpdateState. This is should be fine, but it will be good to breadcrumb
incase we start to see some crashes on firstrun with this interaction.
The setup executable could modify the registry state directly but it is
cleaner to have the one master of the registry state value.
Fixes: #13771
To facilitate code investigation and issue repro attempts, we should log the
engine's current keyboard, language code, and model when reporting errors.
Fixes: KEYMAN-ANDROID-71V
(As this adds Sentry logging, I needed a reliable error with inspectable logs
for development.)
Test-bot: skip
Fixes: #13177
We now need to install sdkmanager through a different Homebrew package /
"cask". This does get us `sdkmanager`, but it has a new default location
for its Android SDK, while our builds still refer to the old location
under the home directory. The build script thus needs a bit of tweaking
to force `sdkmanager` to operate based on the location we've previously
referred to.
Additionally, macOS machines typically default to the zsh terminal these
days, so the old profile auto-config doesn't work. This adds and
documents example profile script that can be used to configure a macOS
dev machine's terminal environment.
The old build config on TC did only run the tests for `keyman-config`.
#13754 missed that fact, and so this script it previously did run all
Linux tests. The integration tests failed because they were missing the
necessary setup.
This change runs all Linux tests without the integration tests.
Follow-up-of: #13754
Test-bot: skip
The recent update of one of the `docker/build-push-action` dependency referenced in the `gha-ubuntu-packaging` dependency now adds the `.dockerbuild` log files as artifacts which confuses the `prepare_api_verification` step. This change now limits the artifacts we pass to the API verification to the keyman package related ones.
The recent update of one of the `docker/build-push-action` dependency
referenced in the `gha-ubuntu-packaging` dependency now adds the
`.dockerbuild` log files as artifacts which confuses the
`prepare_api_verification` step. This change now limits the artifacts
we pass to the API verification to the keyman package related ones.
Test-bot: skip
This change fixes the fix that #13891 implemented. However that only used the string `VERSION` instead of the variable... Fixes the package builds of `stable-18.0` branch.
Fixes: #13891
Replaces: #13956
This change fixes the fix that #13891 implemented. However that only
used the string `VERSION` instead of the variable... Fixes the package
builds of `stable-18.0` branch.
Fixes: #13891
Test-bot: skip
