Skip to content

Build PostgreSQL

Build PostgreSQL #612

Triggered via schedule March 19, 2026 05:53
Status Success
Total duration 33m 9s
Artifacts 17

postgresql.yml

on: schedule
get-versions  /  Generate output
9s
get-versions / Generate output
Matrix: build-postgresql
Fit to window
Zoom out
Zoom in

Annotations

16 warnings
get-versions / Generate output
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
build-postgresql (16.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, dawidd6/action-download-artifact@v7, ilammy/msvc-dev-cmd@v1, marvinpinto/action-automatic-releases@latest. 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/
build-postgresql (16.12)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build-postgresql (16.12)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build-postgresql (15.16)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, dawidd6/action-download-artifact@v7, ilammy/msvc-dev-cmd@v1, marvinpinto/action-automatic-releases@latest. 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/
build-postgresql (15.16)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build-postgresql (15.16)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build-postgresql (14.21)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, dawidd6/action-download-artifact@v7, ilammy/msvc-dev-cmd@v1, marvinpinto/action-automatic-releases@latest. 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/
build-postgresql (14.21)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build-postgresql (14.21)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build-postgresql (17.8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, dawidd6/action-download-artifact@v7, ilammy/msvc-dev-cmd@v1, marvinpinto/action-automatic-releases@latest. 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/
build-postgresql (17.8)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build-postgresql (17.8)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build-postgresql (18.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, dawidd6/action-download-artifact@v7, ilammy/msvc-dev-cmd@v1, marvinpinto/action-automatic-releases@latest. 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/
build-postgresql (18.2)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build-postgresql (18.2)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Artifacts

Produced during runtime
Name Size Digest
postgresql-14.21-config
474 Bytes
sha256:260788221842e7ceb4e29c5cc72437b740f1a0735e140a32aa4b9d34710519f2
postgresql-14.21-src
28 MB
sha256:fb559adee62c5f7645d49b27f6997d82cc8555d0ffd9a99696880e3fdb3894c4
postgresql-14.21-win64
72.5 MB
sha256:a47ac99e82b591dc16a65ad92e374418a6458fb4a13997f5dcb7de97691c895b
postgresql-15.16-config
474 Bytes
sha256:ff9e8e911e029ce9bde3caa332b87ec597dc8228418506105e971cf2bfe1b69e
postgresql-15.16-src
29 MB
sha256:68501e1686166149038b807e273344e9f88e3ed0f2398a6fcd052044abe7d0ac
postgresql-15.16-win64
70.3 MB
sha256:96fcde3e3229798ecc372c5aa64d29e6e8ce30ce6ae500aa9fd3cbfbd68457af
postgresql-16.12-config
474 Bytes
sha256:309442342ad24b0bdfb0d35814a81dbd427e1613c4828b89559e5f703ac474fa
postgresql-16.12-src
31.2 MB
sha256:e9ccdcbaae88ed11e3f437c9ce2553686cc07a1cf255ed0b8d68211b78a85eea
postgresql-16.12-win64
74.3 MB
sha256:d5723de5bc61c10a7fac3c14e5417deaff7ad7d01fea96d124b59ea2b70b3aa4
postgresql-17.8-meson-log
40.2 KB
sha256:ccc971e776b0e45bc4adaf1a551e1a0a5fa67088e4d5abb91f4d48a5112f4f4b
postgresql-17.8-src
26.8 MB
sha256:118fd55e1902c78d32ee1124361143e6fdb3c163ce0d3d6a0bf13c69aaf7501e
postgresql-17.8-test-logs
9.82 MB
sha256:8f61941378360f7323fc9236ca4690dba37269edab1e6972ce3ce85614d35e65
postgresql-17.8-win64
90.3 MB
sha256:e8dd47662e75c94b3cab00933fd9b7e73f14b5e6555da0e71beb0a3cd5fe4e8c
postgresql-18.2-meson-log
40.7 KB
sha256:1a773280f87b1df3e5c0fcbb01b7a203305511da1b671865539d030daec70e18
postgresql-18.2-src
27.9 MB
sha256:f5e4a50eb3e7fef27582e5923cc75983e50b00d39d4470dc98088847bca00d15
postgresql-18.2-test-logs
9.28 MB
sha256:2a500306f0a71f032c861e56529035f019c7aa5abd27eaa46571d1370ecf472b
postgresql-18.2-win64
91 MB
sha256:cb7650f47ead1b0fc259d23be229d35623611fec6aebb59a34e570aaa92fbf58