Release process

Procedure for release

• check new dependencies: mvn versions:display-dependency-updates
• update canary version on evitadb.io
• run documentation tests locally and review them
• all test pass
• copy previous evitaDB format to evitadb.io server and create new backward compatibility test
• run io.evitadb.api.EvitaBackwardCompatibilityTest
• upgrade evitaDB client + server in internal e-commerce suite
• run internal e-commerce suite tests
• run internal e-commerce application, full reindex and review FE is working correctly
• PR to master - release
• review and publish release notes
• write release info to:
  • Discord channel
  • Twitter channel
  • Company channel
• update version to next snapshot in dev
• update supported versions in SECURITY.md
• update latest released version in markdown files
• install new version to internal e-commerce test server