Evan

EDIT: I took these words to heart and reworked this PR to use @Integration instead. Now our tests live under /src/integration-test and can take advantage of all the things I...

> Hhowever when I tried to pull this locally and play around with it when I ran a simple `grails test-app -integration` it resulted with failed tests. I tried to...

yes thanks @harryytsao for the contribution! Were you able to get the app running through Docker via these updated instructions? I haven't tested the Docker build myself since the upgrade...

@drodzewicz Yeah that would be useful. I'd definitely like for it to be automatic since I don't want people to have to remember both what version we're on and also...

I'd like to handle release/milestone labelling in a separate PR. I imagine that will require some thought since we're not really utilizing milestones right now. I do like the idea...

@jmiranda take a look at this when you get a chance. I've only tested the happy path on my local so it's not ready to merge yet but I wanted...

okay, I see that this is failing for integration tests with: ``` WARN groovy.sql.Sql - Failed to execute: SELECT EXISTS (SELECT 1 FROM DATABASECHANGELOG) because: Table 'test.DATABASECHANGELOG' doesn't exist 2024-09-24...

I've tested this change on my local 0.9.x setup and on clean installs via integration tests. It could be useful to further test this for 0.8.x installs just to be...

@jmiranda first off, thanks for testing these thoroughly. Some of the log statements are necessarily gone because I moved the logic from BootStrap.groovy to inside the root changelog.groovy itself, which...

@jmiranda I updated the logs to the following. Turns out the changelog can in fact log properly: ``` 2025-01-14 08:39:29,874 INFO [main] org.pih.warehouse.BootStrap: Executing migrations ... 2025-01-14 08:39:30,401 INFO [main]...