Hi! AuraDB instances are automatically updated to the latest and greatest version. This automatic patch and upgrade management is for us one of the reasons for a managed service. For Neo4j the current release strategy is: internal test instances, then moves on to Free and Pro tiers after that non-production Business Critical en Enterprise instances and finally the production tiers. Only after a successful rollout to production Aura instances the binaries for self-manages deployments and docker containers are released. For far, so good. Unfortunately for us, we encountered some regression issues on our Aura instances. Some of our Cypher queries started to fail in production. Nightly tests are running smooth, local development is all fine, all good except the most important instance. It would really help us, to have a Docker container available before the start of the rollout to aura. Not as the latest version, but as a "Canary" release. Something we can use for our Nightly builds to make sure we are prepared for the upcoming automatic upgrade. Compare this with some kind of: - daily-dangerous from Ubuntu - "Apple Beta Software Program" from Apple - Chrome Canary from Google Chrome This will result in fast feedback and prevention of regression issues along the way. Cheers! Ron
