API keys now work smoothly in changelog and sync features
We've fixed an issue where encrypted API keys weren’t decrypted before use, preventing frustrating 401 errors when regenerating changelog entries or syncing data. Now these features connect seamlessly as they should.
We've focused this update on improving how API keys are handled behind the scenes, making sure they’re properly decrypted before being used with AI providers. This fixes a problem that caused annoying 401 authorization errors when you tried to regenerate changelog entries or generate content from your history.
Reliable access for changelog updates
Now, when you use the regenerate feature in your changelog or generate new content from your history, the system correctly decrypts your API keys so those requests authenticate properly. This means smoother, more reliable operation without needing to troubleshoot connection errors.
Better sync support across providers
In addition to fixing decryptions, we’ve expanded support for the Straico provider in sync routes to help keep your data and operations flowing smoothly. Overall, these improvements mean fewer disruptions when working with your changelog and syncing data, so you can focus on what matters most.