Closed ianliuwk1019 closed 2 days ago
After deploy previous "merge-to-main" (https://github.com/bcgov/nr-fom/actions/runs/9719151861), after verifying database for changes on email update for district email (commit:https://github.com/bcgov/nr-fom/commit/601e1bc8e305976a846d43575072d4169af72775) it did not include this flyway change. It's very strange that we did not know what happened why the latest pending "merge-to-main" deployment did not include changes already merged in "main" branch.
It is strange that PR merge and pending in TEST does have the latest flyway run.
Created this PR with just dummy change from latest main branch to do deployment.
Thanks for the PR!
Any successful deployments (not always required) will be available below.
Once merged, code will be promoted and handed off to following workflow run.
After deploy previous "merge-to-main" (https://github.com/bcgov/nr-fom/actions/runs/9719151861), after verifying database for changes on email update for district email (commit:https://github.com/bcgov/nr-fom/commit/601e1bc8e305976a846d43575072d4169af72775) it did not include this flyway change. It's very strange that we did not know what happened why the latest pending "merge-to-main" deployment did not include changes already merged in "main" branch.
It is strange that PR merge and pending in TEST does have the latest flyway run.
Created this PR with just dummy change from latest main branch to do deployment.
Thanks for the PR!
Any successful deployments (not always required) will be available below.
Once merged, code will be promoted and handed off to following workflow run.
Thanks for the PR!
Any successful deployments (not always required) will be available below.
Once merged, code will be promoted and handed off to following workflow run.