NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules
Go modules, #1167 by repository stars
Latest stable
v1.3.2
Last release 13 days ago
09 Nov 2026
Ships fairly regularly
a new release about every 3 weeks
Nearly every release is documented
notes for 9 of 10 stable releases
Nothing withdrawn
no release was ever pulled
4 years old
155 releases · first in 2023
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Fixes issue where using fewer arguments than the number of arguments would leave the params empty or default.
Full Changelog: https://github.com/electrikmilk/cherri/compare/v1.3.1...v1.3.2
Fixes a silly bug where if there was no file argument, we panicked 🙃
--comments argument.Full Changelog: https://github.com/electrikmilk/cherri/compare/v1.3.0...v1.3.1
Nothing published for this version
[ ! ] File name argument MUST be the first argument. Previously, this could be any argument. This has been done for consistency of arguments.
#define prefix.--action= argument to search action definitions defined in that file. Keep in mind, this will also search any included files.Signing seems to have been fixed in macOS 26 Tahoe, so you shouldn't be required to use HubSign if you are on a machine running macOS 26.
Thanks so much!
Full Changelog: https://github.com/electrikmilk/cherri/compare/v1.2.0...v1.3.0
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Adds 26 client version, and now default outputs Shortcuts that use the new client version.
from search to appear in search, from spotlight to also receive input from macOS Spotlight using ShortcutInput.We now have a Homebrew Formulae for the CLI: https://github.com/electrikmilk/homebrew-cherri
RepeatIndex is now of type integer, so that it can be used for comparison.Full Changelog: https://github.com/electrikmilk/cherri/compare/v1.1.2...v1.2.0
Reverts number() action value type to variable for easy value coercion.
number() action value type to variable for easy value coercion.I created a new version of the Cherri logo I think is much nicer and will allow for the unification of the macOS app icon and the logo. I set out to create a logo like that, one that will last a while.
<img width="324" alt="app_icon" src="https://github.com/user-attachments/assets/7e4a16fa-71b6-47ef-b97d-0c60c22348d4" /> <img width="300" alt="cherri" src="https://github.com/user-attachments/assets/7b5bc7e4-d775-43eb-bb2c-dbdc1d9b8df7" /> <img width="300" alt="cherri_new_playground" src="https://github.com/user-attachments/assets/497771fb-e270-402a-87c8-4d325981a797" /> <img width="1080"alt="header" src="https://github.com/user-attachments/assets/7eacf799-d58d-4205-bf8b-3a345dd43cd5" />
This will be merged later when iOS 26, macOS 26, etc., are released to the public in mid-late September, which will likely coincide with the next release.
Full Changelog: https://github.com/electrikmilk/cherri/compare/v1.1.1...v1.1.2
Nothing published for this version
Nothing published for this version
I noticed a bug in the playground where if you made an empty file, then deleted that file, it could reset all of your files back to the example hello.
jsonRequest(), formRequest() and fileRequest() actions. These actions were missing crucial identifiers in the last release; apologies.I noticed a bug in the playground where if you made an empty file, then deleted that file, it could reset all of your files back to the example hello.cherri file. This has been fixed.
#import functionality.Full Changelog: https://github.com/electrikmilk/cherri/compare/v1.1.0...v1.1.1
This comes with the disadvantage and is a breaking change, as it requires most actions to be included specifically; however, the compiler looks for wh…
count() to one action. New documentation.var type with variable.This is a notable new feature that is now the way that most actions are defined in the compiler. We now include files for each category of actions with definitions that use the following syntax:
#define action default mac|!mac v16> v18< 'com.example.app' actionName(text param: 'WFKey' = "Default Value"): text {
"WFParam": "Additional Param Value"
}
These are action definitions that create an action definition in the compiler in a pre-processing step in https://github.com/electrikmilk/cherri/pull/95.
This allows for defining actions not defined in the action includes, which only includes standard Shortcuts actions. This is primarily meant to be a way to define any action without needing to use a raw action within a copy-paste or custom action.
This also means alternative standard Shortcut libraries could be written in Cherri. You could put arguments in whatever order you like and adjust argument value types.
Because actions have been moved to being defined in text in files, this comes with the advantage of being able to separate them into more categories of files and make them files you include, to optimize memory usage for larger shortcuts or smaller shortcuts, except for the basic actions and types. For more, see basic.cherri.
#include 'actions/scripting'
This comes with the disadvantage and is a breaking change, as it requires most actions to be included specifically; however, the compiler looks for which action needs which include, so it will tell you what to add when it comes across an action that is not defined but exists in one of the action includes.
The compiler is now fully self-documenting with titles and descriptions for actions and categories of actions. You can use the --docs= argument to view all of the actions in a category. Use --help for all available categories.
cherri --docs=web
Improvements have been made to expression parsing, allowing comments that follow action calls to be excluded as expression operands. Additionally, expressions can now start with parentheses, and validation of each value in the expression has been implemented.
I'm building for x86_64 and arm64 Linux using Go, which should work on most distributions.
--open argument.Ask global. Read documentationFull Changelog: https://github.com/electrikmilk/cherri/compare/v1.0.1...v1.1.0
Nothing published for this version
Nothing published for this version
Nothing published for this version
BREAKING CHANGE This changes the syntax as outlined in the MR:
BREAKING CHANGE This changes the syntax as outlined in the MR:
Before
rawAction("is.workflow.actions.documentpicker.save", [
{
"key": "WFAskWhereToSave",
"type": "boolean",
"value": "true"
},
{
"key": "WFSaveFileOverwrite",
"type": "boolean",
"value": "false"
}
])
After
rawAction("is.workflow.actions.documentpicker.save", {
"WFAskWhereToSave": true,
"WFSaveFileOverwrite": false
})
Read full raw action documentation
reflect.Kind iota for checking reflected types instead of string constants.Full Changelog: https://github.com/electrikmilk/cherri/compare/v1.0.0...v1.0.1
Nothing published for this version
As you may or may not know, multiple conditions were recently implemented in Shortcuts. This is great news for the most part, as it's with the caveat
As you may or may not know, multiple conditions were recently implemented in Shortcuts. This is great news for the most part, as it's with the caveat of all OR or all ANY logical comparison, but it's better than not having multiple condition comparisons. I guess I agree that it's technically simpler this way.
You can now use typical multiple condition syntax, just with all the same logical operators.
if variable == "value" && otherVariable == 2 {
// ...
}
Shortcuts only allows some comparisons for certain value types. This implements type checking of the values being used for a conditional. This needed to be fixed for a while. I was always technically aware of this, and now it's finally fixed.
We now throw an error if the type of conditional (e.g. ==) you are using does not support the type of value you are comparing. If we didn't, and before this was fixed, this would just produce an invalid Shortcut, and we misled you that you were able to make that comparison.
runSelf() action decompilation.downloadURL()).getValue() action as dictionary['key'] if you are using it as a variable value.The first explicit comment action (e.g., comment('Hello')) in a Shortcut will now be added to the top of the final Shortcut if you are using a defined custom action.
This also comes with the benefit that we now don't add the custom actions header if you are not using any custom actions. We needed this at first to make sure we weren't adding the first comment to the top every time, and above any actions before it.
This implements action output types properly. This has always kind of existed, but was skipped over in the compiler until now. Not all actions have output types defined, just the ones that have a definite type of output, like text or a number.
This also implements output types for custom actions. Custom actions go through the same type checks as normal actions, so I wanted to also allow custom actions to have their own custom output type to check their usage against.
The preview used in the playground and documentation sites has been improved a lot in just the last release. A lot of bugs have been fixed, and it can now display the details and setup of a Shortcut, as well as how it handles no input. This means pretty much all of the Shortcut metadata is now in the preview.
The docs are now better with a better preview. However, there is also now a preview for definitions like colors and glyphs, which we could have done before the update to the preview.
The other definition previews are mostly powered by those new updates, however. This also means we could add a preview for import questions now that we have a details modal with a setup tab.
\n). This was printed out as an actual new line character when printing their definitions.Full Changelog: https://github.com/electrikmilk/cherri/compare/v0.2.9-beta...v1.0.0
Nothing published for this version
Incrementing the delta on output names.
--sigining-server= argument which abstracts what we were doing for the --hubsign argument to allow for any signing server that implements https://github.com/scaxyz/shortcut-signing-server. You only need to supply the URL. This also makes it so we can add more default services in the future, similar to HubSign.Full Changelog: https://github.com/electrikmilk/cherri/compare/v0.2.8-beta...v0.2.9-beta
Nothing published for this version
Refactored the translate actions to use codes instead of the full language name.
base64File() can be used for this instead, and now allows a file to be downloaded, base64 encoded, and then used as a variable for the makevCard() action photo argument. With the previous implementation this would not be possible. Read the documentation for more.comment('Test'))--comments (-c) argument now doubles for decompilation, which means comment() actions will be used instead of text comments.downloadURL() uses this method automatically, other actions like jsonRequest() only allow POST, PUT, etc. but not GET, and GET does not allow for a JSON or Form body.action keyword and start trying to parse the custom action declaration.textValue, we now generate TextOutput as it looks better when viewing the Shortcut.18.4.number() action decompilation.rotateImage() to rotateMedia() as this action can be used to rotate an image or video.Full Changelog: https://github.com/electrikmilk/cherri/compare/v0.2.7-beta...v0.2.8-beta
Nothing published for this version
This is primarily to hotfix two issues:
This is primarily to hotfix two issues:
Anyways…
You can now sponsor me through RoutineHub's Creator Program! Special thanks to them for onboarding me to this program.
Full Changelog: https://github.com/electrikmilk/cherri/compare/v0.2.6-beta...v0.2.7-beta
Check previous release for more recent major changes.
You can now import a Shortcut from an iCloud link or a local unsigned Shortcut file.
You can now import a Shortcut from an iCloud link or a local unsigned Shortcut file.
Note: It may not work perfectly or produce a Shortcut that will compile. If your shortcut uses Get Variable or a control flow action output you will need to do a little work to get it to work.
--import= flag in the CLI. This will create a Cherri file based on the Shortcut inputted in the same directory or optionally at the --output= path.Try it on the playground now! Click the cloud download icon to get started.
<img src="https://github.com/user-attachments/assets/b48354dd-5631-47a8-8968-74fb997db485" width=300/> <img src="https://github.com/user-attachments/assets/cc965bf3-a378-4a34-aa42-1bff24568145" width=300/>
--import flag. So now to open the compiled Shortcut use the --open flag.mac definition being false.plist package among our string builder implementation in the codebase, it's a bit awkward. We have an opportunity ostensively to build our plist faster, then marshal it using the package we now use to unmarshal imported Shortcuts. This should lower the memory we are using to build the plist data by not having a string builder with the plist we've generated so far in memory while we are building it.Full Changelog: https://github.com/electrikmilk/cherri/compare/v0.2.5-beta...v0.2.6-beta
One column per quarter.