alf.io - The open source ticket reservation system for conferences, trade shows, workshops, meetups
This is a bugfix release for regressions/bugs introduced with 2.0-M4-2402
Full Changelog: https://github.com/alfio-event/alf.io/compare/2.0-M4-2402-1...2.0-M4-2402-2
This is a bugfix release for regressions/bugs introduced with 2.0-M4-2402
Full Changelog: https://github.com/alfio-event/alf.io/compare/2.0-M4-2402...2.0-M4-2402-1
Full Changelog: https://github.com/alfio-event/alf.io/compare/2.0-M4-2304...2.0-M4-2402
please note that all security fixes are related to the Backoffice application. Some of them impact only multi-tenant deployments. The "public" application was not impacted.
thanks to @huntr-helper contributors: @lujiefsi and @yelprofessor !
please note that both security fixes are related to the Backoffice application. The "public" application was not impacted.
thanks to @huntr-helper contributors!
This release contains a fix for CVE-2022-22965 a.k.a. "Spring Shell". Although we should not be impacted directly (we use jetty instead of tomcat as web server), we advise you to update your instance.
This is the fourth milestone on our way to Alf.io v2. See Roadmap and full Changelog
this release includes some breaking changes in the database schema, making it incompatible with older versions of alf.io. It is strongly recommended to perform a full backup of your database before installing it, so that if anything goes wrong you can rollback to the latest 2.0-M3
This release contains a security fix for the following CVEs:
update is strongly recommended
2.0-M4.RC1 introduced some breaking changes in the database schema. If you're updating from 2.0-M3, it is strongly suggested to perform a full backup of your database before installing it, so that if anything goes wrong you can rollback to the latest 2.0-M3
This release contains a security fix for the following CVEs:
update is strongly recommended
This release contains a security fix for the following CVEs:
update is strongly recommended
This release fixes also some errors in the migration files.
2.0-M4.RC1 introduced some breaking changes in the database schema. If you're updating from 2.0-M3, it is strongly suggested to perform a full backup of your database before installing it, so that if anything goes wrong you can rollback to the latest 2.0-M3