@mark-robustelli I haven't tested it again since, but I build a docker image using the base fusionauth image (fusionauth/fusionauth-app) because I have a custom plugin and kickstart file.
So my upgrade process is simply to update the base fusionauth image in my dockerfile, and then update my container in Azure. This has worked fine since 1.56, and updated through all the updates with migrations.
Edit: I just noticed that the downloaded schemas does contain a migration for 1.65, and running it on the database does make the container start now. Would have expected this migration to run on start up like the other updates though.

I upgraded my FusionAuth instance (self-hosted container) from 1.64.1 to 1.65.0, but the container never starts.
Reading the logs during start up I found the following issue

SQL: SELECT internal_authentication_keys_id FROM instance LIMIT 1"} 
Cause: org.postgresql.util.PSQLException: ERROR: column \"internal_authentication_keys_id\" does not exist"} 
...
...
...
ERROR org.primeframework.mvc.guice.GuiceBootstrap - Unable to start the server. Exception:"}

So the app is clearly expecting a schema change that my database doesn’t have.

What’s confusing is:

There are no visible migration scripts running during startup
Release notes don’t mention a migration step
But 1.65 clearly assumes this column exists in instance

I downloaded the schemas for both versions and instance.internal_authentication_keys does exist on 1.65.0, but not 1.64.1