commit 756f71a25cf1ae485b33704c2ef313b979c301b4
Merge: 1086c12c4 9eeb6be69
Author: Eberhard Beilharz <ermshiperete@users.noreply.github.com>
Date: Mon Nov 17 08:32:27 2025 +0100
Merge pull request #15132 from keymanapp/chore/linux/changelog
commit 1086c12c4e17faab7ce5bc597d448fc75614e513
Merge: d7e160cc3 b5b916abb
Author: Marc Durdin <marc@durdin.net>
Date: Sat Nov 15 06:48:45 2025 +0100
Merge pull request #15175 from keymanapp/fix/windows/cherry-pick/14342-invalid-data-type-for-regkey
fix(windows): add check a fix for registry datatypes 🍒 🏠
commit b5b916abbfec4ee3ddc83de457c716552cbec72a
Author: rc-swag <58423624+rc-swag@users.noreply.github.com>
Date: Mon Jul 28 16:54:37 2025 +1000
fix(windows): remove dead code
commit b04229efe5a2451c2cc8e368128d018e51b62e8e
Author: rc-swag <58423624+rc-swag@users.noreply.github.com>
Date: Thu Jul 24 16:59:41 2025 +1000
fix(windows): free the correct object KeyboardToggleReg
commit 5bf1f635a6f4e36791aa0e8b5a9f4df80467abca
Author: rc-swag <58423624+rc-swag@users.noreply.github.com>
Date: Tue Jul 15 16:27:14 2025 +1000
fix(windows): add check a fix for registry datatypes
Fixes: #14342
The Windows system level keyboard hotkeys controlled in
registry have sometimes been incorrectly written as
a DWORD datatype. There 106 events in sentry for just
July. When opening the Windows setting dialog and the registry
has DWORDS it will show unassinged in the dialog if apply
is pressed it will convert the keys to REG_SZ.
This fix follows a similar pattern it will check the data
type of the registry key if it is DWORD it will remove it
and add a new key of the same name as REG_SZ and set it to
the unassigned value.
Fixes: KEYMAN-WINDOWS-4NK
commit 9eeb6be6953cdca52242adb9999e60d18a623bf8
Author: Eberhard Beilharz <eb1@sil.org>
Date: Mon Nov 10 17:06:42 2025 +0100
chore(linux): Update debian changelog
commit d7e160cc3639b685418a5a875912e1f01a22b5b6
Merge: 8362fb0e9 97d7266e3
Author: Eberhard Beilharz <ermshiperete@users.noreply.github.com>
Date: Tue Nov 4 19:29:21 2025 +0100
Merge pull request #14964 from keymanapp/chore/linux/changelog
chore(linux): Update debian changelog 🏠
commit 97d7266e31ac786a9dd7c990d9c2009a576f5aa1
Merge: 392d85a1a 8362fb0e9
Author: Eberhard Beilharz <ermshiperete@users.noreply.github.com>
Date: Mon Nov 3 14:44:57 2025 +0100
Merge branch 'stable-18.0' into chore/linux/changelog
commit 8362fb0e999711e27e8dd059e0928c0b30c9d32e
Merge: 376b5fd61 f7d1b6ceb
Author: Marc Durdin <marc@durdin.net>
Date: Mon Nov 3 05:19:06 2025 +0100
Merge pull request #15068 from keymanapp/maint/resources/npm-publish-use-v18-env-var
maint(resources): use VERSION_ENVIRONMENT var for v18 🏠
commit 376b5fd6121376d261ee25ea6b44521b3cd27b32
Merge: b068e0af4 d7b16aece
Author: Marc Durdin <marc@durdin.net>
Date: Fri Oct 31 15:39:22 2025 +0100
Merge pull request #15081 from keymanapp/chore/18.0/vs2022
chore(windows): VS2022 patch for stable-18.0 🏠
commit d7b16aece9595414b573854d894136cc191bd26c
Author: Marc Durdin <marc@durdin.net>
Date: Thu Oct 30 16:31:45 2025 +0100
chore(windows): upgrade VC++ projects to v143 (VS2022)
Test-bot: skip
Build-bot: skip release:developer,windows
commit f7d1b6ceb544a966ee5d0635188725599e8e1bbd
Author: Marc Durdin <marc@durdin.net>
Date: Fri Oct 31 11:36:32 2025 +0100
maint(resources): use VERSION_ENVIRONMENT var for v18
Follows: #15054
Build-bot: skip
Test-bot: skip
commit b068e0af4531d9f0e5ec333658aff5b4399aeacd
Merge: 9a9f82511 e2f5cbd9d
Author: Keyman Server <keyman-server@users.noreply.github.com>
Date: Fri Oct 31 07:39:26 2025 +0100
Merge pull request #15066 from keymanapp/auto/version-stable-18.0-18.0.245
auto: increment stable-18.0 version to 18.0.245
commit e2f5cbd9d7687a299d0dcdc0ab0ca3ca22ed8b02
Author: Keyman Build Agent <buildagent@keyman.com>
Date: Fri Oct 31 01:38:44 2025 -0500
auto: increment stable-18.0 version to 18.0.245
commit 392d85a1ad895dbb48e71f4ebf605d1612fa2b21
Author: Eberhard Beilharz <eb1@sil.org>
Date: Wed Oct 15 12:09:34 2025 +0200
chore(linux): Update debian changelog
Automatic checks made by the Debian l10n team found some issues with the translations contained in this package. You should check the l10n status report for more information.
Issues can be things such as missing translations, problematic translated strings, outdated PO files, unknown languages, etc.