Users with the (paid) additional themes need to update manually this time.

[KevinBatdorf]

Hi all!

So I screwed this up and wanted to put my thoughts out there, and while I have your attention mention a few upcoming features I'll be working on.

First of all, you can get the latest zip file from the dashboard. After you download it, go to the main WordPress plugins page in your admin area, press "Add New", upload the file, and it's fine to override the previous one. That's all you need to do.

Why the update?

When deciding on how to handle updates, since the plugin is not hosted on WordPress.org, I landed on using GitHub since it was very simple to set up, and essentially no overhead cost. However, to keep the repo private, I needed to create an access token to distribute with the plugin to give it access. My "creative" solution at the time was to create a brand new user account with access only to that repo, and give the key only read access.

A few months back, that key was leaked on GitHub and they revoked it. I'm guessing someone uploaded the plugin on GitHub and they auto-detected it. In retrospect the inevitability of that should have been obvious to me, but I was careless. Lesson learned.

I've set up a custom update server on my own infrastructure, and will be able to serve updates from there. The update process is identical, but since previous versions pointed to GitHub, you'll need the latest version that points to the new server. You don't need to add any key or do anything special other than just uploading the new version.

Why now?

I plan to make some updates this year that will require big updates to both the free version and the additional themes. I want to go over them here now (all features will be in the free version).

1. The first feature will be adding a tool for updating multiple code blocks at once throughout your site. This has been requested a lot, and although it will be challenging to get right, I want to focus on this next. This will allow you to apply theme changes and other global type settings to multiple blocks at once.
2. Next I plan to update shiki to it's newest version. It has a lot of breaking changes, but with the above update mechanism in place, it will be easier to migrate over quickly, if you choose to. Nothing will break on the front end of your site, but if you want to use new features on existing blocks, you'll have to migrate them over (they will lock in place otherwise). I hope to make this painless.

I have some more stuff in mind for this year, but those are the big ones. After that it should be easier to add more languages and themes as well, and add support for better custom themes (and dark/light mode switching)

I'd love to hear your thoughts.