If you release a shortcut in this state you can now just release an update normally with the correct version number included and you'll be good to go.

To fix this, I pushed an update today for UpdateKit that will default to "0" as the version number if none is supplied, ensuring the latest version will always be found.

The way UpdateKit worked until now was that if no current version was supplied, it would fail with an error saying you need to supply shortcut data.

This is great if you're testing a release, but if you release something this way, as I did, it's now impossible to update your shortcut. Yikes!

Switchblade SDK adds support for this filter.

Switchblade UI has a bug fix for the escape key misbehaving.

Switchblade adds a new sinceVersion filter to several endpoints, allowing you to get history from a certain version forward. Useful for displaying change logs for all the versions a user has missed (versus just the latest one they've missed).

So this means there will be permissions to allow/prevent users from viewing draft shortcuts they don't own, or draft versions on shortcuts they don't own.

You should update your shortcuts that use UpdateKit to use the newer, more powerful UpdateKit API immediately! If you still use the legacy updater you may not be able to distribute updates starting on Monday.

mikebeas.com/updatekit-api

I *still* need to add permissions for viewing draft shortcuts and versions that weren't created by the current user, but that's like the last thing I need to do.

- Switchblade SDK update is in development with new endpoints to support the permissions and multi-user functionality in Switchblade. It will also include a new option that allows the SDK to throw on API errors, so you can use try/catch flows.

All other functionality is unchanged.
This will probably be the final version of UpdateKit as a standalone shortcut.

For more information about the deprecation: https://www.mikebeas.com/shortcuts/updatekit