2.1.8: Fix collaborator access and GitHub rate-limit handling

What’s changed

• Fixed invited collaborator access when signed in with GitHub but without direct GitHub repo access
• Improved GitHub rate-limit handling so throttling returns a clear 429-style message instead of looking like a permission failure

How to upgrade

Follow the full upgrade guide: https://pagescms.org/docs/guides/upgrading-to-2/

Full Changelog: 2.1.7...2.1.8

2.1.7: Simplified collaborator invite sign-in with OTP verification

What's changed

• Simplified collaborator invite sign-in flow
• Added OTP verification components and input UI
• Added collaborator invite token API route
• Added collaborator invite database migration
• Updated login email styling and sign-in flow handling

How to upgrade

Follow the full upgrade guide: https://pagescms.org/docs/guides/upgrading-to-2/

Full Changelog: 2.1.6...2.1.7

2.1.6: Fixed GitHub auth duplicate email repair

What’s changed

• Fixed GitHub sign-in failing when a legacy collaborator stub account tried to update to an email already owned by the real user
• Changed GitHub OAuth sign-in to avoid overwriting user email before post-login repair can run
• Added verified GitHub primary-email based repair for legacy @local.invalid users

How to upgrade

Follow the full upgrade guide: https://pagescms.org/docs/guides/upgrading-to-2/

Full Changelog: 2.1.5...2.1.6

2.1.5: Improve GitHub auth recovery and token failure handling

What’s changed

• Stopped automatic sign-out loops on expired GitHub sessions
• Added a manual re-auth path for GitHub session expiry
• Improved the unable_to_get_user_info message with clearer recovery guidance
• Added minimal GitHub /user failure diagnostics (status, x-github-request-id, x-ratelimit-remaining)
• Invalidated the local app session when a confirmed GitHub auth failure is detected server-side

Why

This release reduces stuck login states caused by revoked or invalid GitHub OAuth tokens, while keeping recovery explicit and minimizing token churn.

How to upgrade

Pull main and deploy 2.1.5.

Full Changelog: 2.1.4...2.1.5

2.1.3: Simplify cache

What’s changed

• Simplified the collection/media cache internals and removed obsolete cache meta fields
• Made folder snapshot writes atomic and kept branch reconcile non-destructive
• Preserved incremental updates only for already-verified direct folders
• Stopped trusting empty folder snapshots and fixed empty/missing Git directories for collections and media
• Refreshed README guidance around cache clearing and environment variables

How to upgrade

Deploy 2.1.3, run npm run db:migrate, and if you are carrying old cache state, run npm run db:clear-cache once.

Full Changelog: 2.1.2...2.1.3

2.1.2: Harden cache consistency for media and tree folders

What’s changed

• Tightened folder cache trust rules so ancestor folders are no longer marked ok from partial local patching
• Fixed a remaining media/tree-mode cache hole where root or parent folders could appear empty or partial
• Applied the stricter shared folder-cache behavior consistently across direct CMS writes and webhook incremental updates
• Continued cache hardening around media and collection folder synchronization

How to upgrade

Upgrade to 2.1.2, deploy, then clear cache_file and cache_file_meta once to remove any previously poisoned cache state.

Full Changelog: 2.1.1...2.1.2

2.1.1: Improved collaborator repo access, caching, media renaming, and rich-text image handling

What’s changed

• Fixed GitHub user access to collaborator repositories
• Improved cache metadata handling and repository caching behavior
• Improved markdown image parsing in rich-text fields
• Fixed brittle image handling in rich-text fields
• Added more renaming options for media
• Added utility improvements for file handling
• Fixed related schema and token handling issues

How to upgrade

Follow the full upgrade guide: https://pagescms.org/docs/guides/upgrading-to-2/

Full Changelog: 2.1.0...2.1.1

2.1.0: Actions, cache improvements, MDX support

What’s changed

• Added the new Actions feature set, including action pages, run tracking, updates, and cancellation support
• Improved cache behavior and related invalidation and reconciliation flows
• Added support for MDX in code fields
• Fixed rich-text media disabling behavior (media: false)
• Fixed additional issues around references, file handling, and collection flows
• Improved UI copy and several repo, entry, and sidebar interactions

How to upgrade

This release includes database migrations for Actions and cache updates.

Follow the full upgrade guide: https://pagescms.org/docs/guides/upgrading-to-2/

Full Changelog: 2.0.2...2.0.3

2.0.2: Improved auth flows, navigation groups, mobile fixes, improved copy, updated email theme

What’s changed

• Added navigation groups in the repo sidebar
• Improved media handling and allowed inserting multiple images in rich-text
• Fixed empty folder handling
• Fixed login issues and added redirect handling for expired auth states
• Improved sign-in and collaborator flows
• Created shared email theme
• Refreshed the configuration UI and invalidated stale config cache
• Switched config persistence to upsert
• Fixed the error layout
• Normalized copy for all empty states and errors
• Fixed additional mobile/sidebar issues
• Cleaned up pages-cms mentions (migrated to pagescms/pagescms)

How to upgrade

Follow the full upgrade guide: https://pagescms.org/docs/guides/upgrading-to-2/

Full Changelog: 2.0.1...2.0.2

2.0.1: Bug fixes and improvements

What’s changed

• Improved GitHub webhook handling
• Added automatic reconciliation of legacy GitHub user records on sign-in for upgraded installs
• Fixed Firefox textarea behavior
• Fixed flashing issues in the editor flow
• Fixed flickering issues on reference field (#363 and #366)
• Improved mobile behavior by closing the sidebar on click
• Added a helper script for migrating collaborators from legacy SQLite/libSQL installs
• Removed the old Vercel cron cleanup endpoint
• Fixed validation issues on rich-text field (#362)
• Fixed additional TypeScript/build issues and general cleanup

How to upgrade

Follow the full upgrade guide: https://pagescms.org/docs/guides/upgrading-to-2/

Full Changelog: 2.0.0...2.0.1