BetterTouchTool Changelogs page

Configuration Help & General Discussion
1

Is there a location where we can read what changed between versions?
I looked around the website, the docs and here on forums, but couldn't find anything.

1 Like
2

https://updates.folivora.ai/bettertouchtool_release_notes.html

It's only updated for stable releases though, not for every alpha.

3

Thanks so much, Andreas!

So 3.674 isn't a stable release or is the page not up-to-date at the moment?
I update bettertouchtool via brew cask and that's how I got that version update.

4

3.674 is the current alpha channel version, so brew cask seems to use the alpha channel

1 Like
5

Ok, pinned the cask to 3.674 until the next stable release for now. Thanks!

6

Hi @Andreas_Hegenberg , I've noticed that some minor stable version are having the same "Release Notes", for example I think the last 2-3 version all of the have the following:

" * Compatibility with the new USB-C Magic Mouse and Magic Trackpad (they also work fine with older BTT versions, just minimal adjustments were made)

  • Fixed issues with Apple Scripts not updating
  • Fixed "Close All Notifications" action for macOS 15.1
  • ChatGPT actions now support streaming / incremental output
  • Floating Menus: Option to disable dragging
  • Floating Menus: Items now can trigger actions when scrolling up/down/left/right on them.
  • Floating Menus: New Predefined Action "Open Specific Submenu In Floating Menu"
  • (Sorry for the many small updates, this was a complex release cycle with lots of under-the-hood changes thus a few more regressions than usual have appeared, and a few more updates than usual were necessary. However it'll be the base for many powerful upcoming features)"

Is this expected?

7

yes, alpha updates and/or updates that are not pushed to users automatically don’t have changelogs most of the time. Usually it’s specific stuff being discussed in some forum threads

8

Do you think it is worth including maybe a link to the thread in the forum where the specific issue has been discussed. I know that release notes/change log can sometime be hard/time-consuming to compose, but including the links (if this is easier for you, compared to the describe the actual fix) gives some traceability and the users can know what has been fixed.

Thank you.

1 Like
9

I tried in the past but never found a way of adding such info that fit my workflow. Just linking to a thread without saying what I did also causes confusion.

I'm usually going through the changes and updating the changelogs once a version hits the stable auto-update channel. If there are specific things I need to be tested I'm also updating the changelog in the alpha / manual update channels.

10

Thanks Andreas.