Switchblade v1.3.1 has been released. This includes a critical bug fix that could prevent unauthenticated users from seeing public versions or shortcuts.
24.12.2024 20:34
👍 0
🔁 1
💬 0
📌 0
Switchblade v1.3.1 has been released. This includes a critical bug fix that could prevent unauthenticated users from seeing public versions or shortcuts.
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!
A new version of the UpdateKit API has been deployed with a new safeguard.
Earlier this week I released a new shortcut, but I made the insanely goofy mistake of not filling in the current version of the shortcut in my UpdateKit call.
Ooh, 13,500, an even hundred, nice and round!
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).
New versions of Switchblade + Switchblade SDK + Switchblade UI are out now!
NOW AVAILABLE:
Switchblade 1.2.0
- Adds multi-user support
Switchblade UI 1.1.0
- Adds user management and permissions features
Switchblade SDK 1.1.0
- Adds support for Switchblade 1.2.0 features
www.reddit.com/r/shortcuts/...
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.
So... good news! I decided to take another look at the permissions system and see if I could get the "view"-type permissions working, and I've found a way to do what I originally wanted. It's a method I wanted to avoid initially but after thinking about it some more I think it's the right approach.
Legacy UpdateKit has now been deprecated. The web pages have been removed and the BlackBox API has been shut down.
The UpdateKit API is now the only UpdateKit there is!
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
FINAL REMINDER:
On Monday, September 18, Apple will release iOS 17. On that day, the legacy UpdateKit shortcut will be removed from download. The API that supports legacy UpdateKit versions will be shut down.
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.
Sat down to add one or two more things to the Switchblade update and got sidetracked adding something I had initially decided to punt to a further release.
When multi-user launches you'll have the ability to filter shortcuts and versions by the creator.
- 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.
Ongoing work:
- Making progress on full multi-user support for Switchblade servers. The bulk of the work on the permissions backend has been completed, I think. Frontend work for Switchblade UI will start soon.
REMINDER: The UpdateKit standalone shortcut will be discontinued and removed from download this month when iOS 17 launches to the public!
Migrate your shortcuts to the UpdateKit API for faster, more-powerful update checks!
Switchblade UI works great on Cloudflare Pages with no changes! https://pages.dev
switchblade-sdk is now available on npm due to github's package registry requiring users to authenticate to install public packages.
switchblade-ui has been updated to v1.0.1 with the new install source.
https://www.npmjs.com/package/switchblade-sdk
NOW AVAILABLE:
- Switchblade v1.1 with new several features
- Switchblade UI: an admin panel for Switchblade
- Switchblade SDK: a Node package for interfacing with Switchblade servers
https://www.reddit.com/r/shortcuts/comments/13n0h6g/announcing_switchblade_v11_switchblade_ui_and_the/
I think they're done… I'm going to be preparing some screenshots, squashing git commits, pushing code to public repos, and announcing on Reddit soon!
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
UpdateKit 10.0 will be released when iOS 17 enters beta, probably on June 5th with the first day of WWDC.
UpdateKit 10 adds a notice about the previously announced deprecation and discontinuation of UpdateKit as a standalone shortcut to encourage developers to migrate to the UpdateKit API.
I’m working on:
- The next update to Switchblade with some quality-of-life improvements around MFA
- A JS/TS SDK you can install into your project for easy interaction with Switchblade servers
- A control panel for Switchblade you can install and run anywhere (you can always use a different one)
I’ll mirror any new Mastodon posts over here until one of the services wins!