Nicely put @corticalcode 
I’ll finish the automation then link to the Github repo here. I’ll most likely add the disk image(s) to the Github releases and will also host a copy myself. Changes to build.sh to enable notarization will be patches in my repo for now, hopefully they can be added to the mkvtoolnix repo if suitable. I’ll raise a pull request when it’s done.
It would be great if you could release your version and possibly future versions as well.
I think many MKVToolNix users—myself included—don’t have the ability to do this work. I, for one, am very grateful to people like you and corticalcode who make it possible for others to continue using this wonderful tool on an ARM Mac!
Ah, that’s a whole other process I hadn’t been aware of until now. That’s the only reason I hadn’t done that for the binaries I used to provide.
Here is a copy of the notarized disk image of MVKToolNix GUI 98.0 for Apple Silicon (ARM64), for testing purposes.
I’ve installed and tested it on macOS 26.4.1 and 15.7.5, but I don’t have access to 13.x or 14.x installations. (MVKToolNix GUI 98.0 should run on those versions too, I might create a quadruple-boot Mac to test all four…)
Any reports of success or failure will be very gratefully received!
Hello!
I’ve now finished adding automated notarization to the repo, released it as v1.0 and submitted a pull request to the mkvtoolnix repo in the hope that my installation script patches become part of the main source.
The repo is public and can be found on Github.
Edit: links are intentionally broken, please see my next post.
The notarized disk image can be downloaded from the Github v1.0 release or my own hosted copy should that be unavailable. They’re the same file.
Hope this helps! Any reports of success or failure will be gratefully received 
Hi folks,
I’ve updated the Github repo to v1.1 and deprecated the previous disk images as I had the wrong git clone command in my script. Instead of cloning the tag release-98.0 it was cloning the whole repo into a directory called release-98.0. This meant that the disk images contained up-to-date builds, i.e. including changes made since 98.0 was released 
I’ve corrected my error and released v1.1 which includes a notarized disk image that actually includes MVKToolNix GUI 98.0. The image can be downloaded from the Github v1.1 release file or my own hosted copy should that be unavailable.
Sincere apologies for wasting your bandwidth, normal service will be resumed as soon as possible.
The git clone problem went deeper than I thought: the disk image in v1.1 was built with Qt 6.11 instead of Qt 6.10
It will have been fully functional but I’m a stickler for detail so I’ve addressed the issues, updated the Github repo to v1.2 and rebuilt the notarized disk image from scratch so that it matches Release 98.0 exactly.
The disk image can be downloaded from the Github v1.2 release file or my own hosted copy should that be unavailable.
‘Fail fast’ is a good maxim but ‘embarrass yourself in front of a new community’ is what I’m trying to reconcile myself with today 
I’ve learned a lot this week and it’s only Tuesday.
Hope this helps!
Don’t worry. Any maintainer who’s been at it long enough has gone through borked releases multiple times, including myself 