Skip to content

Conversation

@snadrus
Copy link
Contributor

@snadrus snadrus commented Nov 27, 2025

Allow reverting, where authors authorize it.
This provides an avenue for "buyer's remorse" where upgrades with migrations turn out badly.

revert/* authors:

  • Since db sql is reentrant, no need to delete tables.
  • Migrations MUST migrate back
  • SQL INSERTs: are they defaults or do they trigger something?
  • Note that the db gets fully upgraded TO THIS RELEASE first.
  • not every SQL needs a revert, but all should indicate if they're able to revert.

@snadrus snadrus marked this pull request as ready for review December 2, 2025 20:03
@snadrus snadrus requested a review from a team as a code owner December 2, 2025 20:03
@snadrus snadrus changed the title Revert db schema CLI Downgrade db schema CLI Dec 3, 2025
@snadrus snadrus changed the title Downgrade db schema CLI Downgrade db schema via Curio Toolkit Dec 5, 2025
Copy link
Collaborator

@magik6k magik6k left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, maybe would consider instructing users to make a backup, they are likely already recovering from a disaster so best to add some guardrails

@snadrus snadrus merged commit cb92510 into main Dec 9, 2025
19 checks passed
@snadrus snadrus deleted the revert branch December 9, 2025 22:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants