How risky is upgrading from 1.1.24.04 to current 1.1.30.03?

[enigment]

I have 1.1.24.04 from Dec 17, 2016 installed.
As of today, current version is 1.1.30.03 from April 4, 2018.

I'm not using AHK for anything super cosmic, mostly text replacements, but I'd still like it to keep working.
It's also important that it not make my system unstable (of course).

How risky would you think it is for me to upgrade to the current version now?
Thanks for any thoughts.

[Chunjee]

I think absolutely required. Reading https://www.autohotkey.com/docs/AHKL_ChangeLog.htm it looks like mostly just fixes.

The addition of Object.Count() is why I say required. That was added in 1.1.29.00

[gregster]

Even if you had a problem, you could still downgrade again to v1.1.24.04 or another version (most recent versions are still available on our download page and even older ones on Github).
No AHK version makes any critical changes to your system...

Btw, the latest version 1.1.30.03 is from April 4, 2019, not 2018.

[swagfag]

the changes most likely to break something would be 1.1.27.00's #MenuMaskKey if u have WinKey hotkeys and 1.1.28.00's "hotstring recognizer [to] reset when focus changes instead of just when the active window changes."

[enigment]

Thanks folks. Sorry about the 2018/19 typo, my bad.

I do have Windows key hot keys. What do I need to do so things work correctly with the current version?

[Chunjee]

I do have Windows key hot keys. What do I need to do so things work correctly with the current version?

Install, lol

[enigment]

I do have Windows key hot keys. What do I need to do so things work correctly with the current version?

Install, lol

I was referring to @swagfag's post above, which I though meant that some things might break after upgrading to the current version.

Not so?

[gregster]

Hard to say without knowing your code. But then it only affects specific use cases of the Win key (see the change log) anyway.

This could be relevant, for example:

The hotkeys ~LWin:: and ~RWin:: no longer suppress the Start Menu. See #MenuMaskKey for details and a workaround.

Best way is to just test it... like I said, you can revert easily (or use the workarounds).

[jeeswg]

- I've never had any problems with scripts when updating the AHK exe.
- The only times problems have occurred, has been in the short time period after a big update has been released, and bugs are discovered and fixed.

- I didn't have any problems re. the mask key. Could someone give one or more actual before/after examples of possible mask key problems? (I.e. code before, and new code with workarounds.) The situation is not especially clear from just reading the documentation. (Also, any info as to why the change was made, would be useful.) Thanks.