You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for your work on Sequent — it’s an incredibly useful tool for working with Event Sourcing.
I recently updated Sequent to the latest version from the GitHub repository, and it broke some parts of my project. For example, I noticed that certain functions and procedures in the database stopped working, and the table structures appear to have changed.
This isn’t a big issue for me at the moment since I’m working on a development project. However, I’d like to know if there’s a centralized way to track major changes in the project — such as migrations, schema updates, and the removal of old functions and procedures.
Do you maintain a specific location (release notes, documentation, changelog) where such updates are announced? It would be helpful to understand the best practices for keeping my project aligned with new updates.
Looking forward to your advice, and thank you again for your efforts on Sequent!
The text was updated successfully, but these errors were encountered:
Thank you for your work on Sequent — it’s an incredibly useful tool for working with Event Sourcing.
I recently updated Sequent to the latest version from the GitHub repository, and it broke some parts of my project. For example, I noticed that certain functions and procedures in the database stopped working, and the table structures appear to have changed.
This isn’t a big issue for me at the moment since I’m working on a development project. However, I’d like to know if there’s a centralized way to track major changes in the project — such as migrations, schema updates, and the removal of old functions and procedures.
Do you maintain a specific location (release notes, documentation, changelog) where such updates are announced? It would be helpful to understand the best practices for keeping my project aligned with new updates.
Looking forward to your advice, and thank you again for your efforts on Sequent!
The text was updated successfully, but these errors were encountered: