Rename drift-report inputs to pre-deployment-report #533
Buster-Darragh-Majorend-to-end-test.yml
on: pull_request
Matrix: migrations-community
Matrix: migrations-enterprise-no-comparison-support
Matrix: migrations-enterprise
Matrix: state-enterprise
Annotations
9 errors and 9 warnings
|
migrations-enterprise-no-comparison-support (macos-latest)
Drift analysis error: Snapshot history not supported for database type H2 Exception: Snapshot history not supported for database type H2
|
|
migrations-enterprise-no-comparison-support (macos-latest)
Drift analysis error: Snapshot history not supported for database type H2 Exception: Snapshot history not supported for database type H2
|
|
migrations-enterprise-no-comparison-support (macos-latest)
Drift analysis error: Snapshot history not supported for database type H2 Exception: Snapshot history not supported for database type H2
|
|
migrations-enterprise-no-comparison-support (ubuntu-latest)
Drift analysis error: Snapshot history not supported for database type H2 Exception: Snapshot history not supported for database type H2
|
|
migrations-enterprise-no-comparison-support (ubuntu-latest)
Drift analysis error: Snapshot history not supported for database type H2 Exception: Snapshot history not supported for database type H2
|
|
migrations-enterprise-no-comparison-support (ubuntu-latest)
Drift analysis error: Snapshot history not supported for database type H2 Exception: Snapshot history not supported for database type H2
|
|
migrations-enterprise-no-comparison-support (windows-latest)
Drift analysis error: Snapshot history not supported for database type H2 Exception: Snapshot history not supported for database type H2
|
|
migrations-enterprise-no-comparison-support (windows-latest)
Drift analysis error: Snapshot history not supported for database type H2 Exception: Snapshot history not supported for database type H2
|
|
migrations-enterprise-no-comparison-support (windows-latest)
Drift analysis error: Snapshot history not supported for database type H2 Exception: Snapshot history not supported for database type H2
|
|
migrations-enterprise-no-comparison-support (macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hashicorp/vault-action@v3.4.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
state-enterprise (macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hashicorp/vault-action@v3.4.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
state-enterprise (ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hashicorp/vault-action@v3.4.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
migrations-enterprise (ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hashicorp/vault-action@v3.4.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
migrations-enterprise-no-comparison-support (ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hashicorp/vault-action@v3.4.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
migrations-enterprise (macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hashicorp/vault-action@v3.4.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
migrations-enterprise-no-comparison-support (windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hashicorp/vault-action@v3.4.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
migrations-enterprise (windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hashicorp/vault-action@v3.4.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
state-enterprise (windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hashicorp/vault-action@v3.4.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
flyway-community-pre-deployment-report-macos-latest.html
Expired
|
238 KB |
sha256:0268fedb9548d0b0fd6eb7d019659f1d4b31b911e549babcf0059ca57388e10d
|
|
|
flyway-community-pre-deployment-report-ubuntu-latest.html
Expired
|
238 KB |
sha256:69ba10c45191d124f6fe206beb637217308fd140378ce01276b19efcfa06e047
|
|
|
flyway-community-pre-deployment-report-windows-latest.html
Expired
|
239 KB |
sha256:b41f68ff6d6f89f4df7c11ee3b969fc6318d98f636dc671ad2629fc067c17229
|
|
|
flyway-pre-deployment-report-h2-macos-latest.html
Expired
|
248 KB |
sha256:a29a2056788e52b9e35df87954da8d68f46e8ed299cc78924da6578c9910045c
|
|
|
flyway-pre-deployment-report-h2-ubuntu-latest.html
Expired
|
248 KB |
sha256:bb4313921dc158ce4ba90928ad0ae67459c8b62704fb3e9a947cceea45aeb71a
|
|
|
flyway-pre-deployment-report-h2-windows-latest.html
Expired
|
248 KB |
sha256:f021a64bdd24e33c718826ee5303d42c381722dac70c849ecfbc7cb167b38c12
|
|
|
flyway-pre-deployment-report-macos-latest.html
Expired
|
248 KB |
sha256:291d63f005e266cafc557d12d0608c8318c9ce57bd1b3ebc87586e977c9520ad
|
|
|
flyway-pre-deployment-report-ubuntu-latest.html
Expired
|
248 KB |
sha256:59a7395aa35c598dd66e4842e974cf58d76a280b9f4349c870c5f5e941656c01
|
|
|
flyway-pre-deployment-report-windows-latest.html
Expired
|
249 KB |
sha256:2149f576c2d5f52ae37e5ee444ccf8d39b7ef80d07d0cc0ad06a2b7a9e7faa5e
|
|