Fixes for Changelog Save Reliability
#Reliable saving of changelog entries
We resolved issues that could prevent changelog entries from saving correctly in the admin interface. These fixes ensure that when you click “Create Entry” or “Save”, the changes are persisted reliably in Supabase.
The system now provides clearer server‑side validation errors if something is missing or malformed, instead of silently failing.
#Supabase integration hardening
Our Supabase integration for changelog storage has been strengthened. We now perform more explicit checks around table existence, RLS policies, and write access before completing a save.
If anything in the environment is misconfigured, the admin now receives actionable feedback pointing to the root cause.
#Better handling of drafts vs published
The admin experience around drafts has been polished so it’s easier to see which entries are still in progress. Draft entries show clearly in the list view and in the editor, while the public site only shows fully published updates.
This helps keep internal work‑in‑progress separate from the official public changelog.
Improvements
- Fixed intermittent failures when saving new changelog entries
- Hardened Supabase RLS and table checks for the
changelog_entriestable - Improved distinction between draft and published entries in admin
- Added detailed server logs for troubleshooting save operations