Skip to content

chore: pin erpl-proto to v2026.9.2.1 and empty the known-failure list… #703

chore: pin erpl-proto to v2026.9.2.1 and empty the known-failure list…

chore: pin erpl-proto to v2026.9.2.1 and empty the known-failure list… #703

name: Main Extension Distribution Pipeline
on:
push:
paths-ignore:
- '**/README.md'
pull_request:
workflow_dispatch:
permissions:
id-token: write # This is required for requesting the JWT
contents: read # This is required for actions/checkout
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}-${{ github.head_ref || '' }}-${{ github.base_ref || '' }}-${{ github.ref != 'refs/heads/main' || github.sha }}
cancel-in-progress: true
jobs:
duckdb-stable-build-v145:
name: Build v.1.4.5 extension binaries
uses: ./.github/workflows/_extension_build.yml
secrets: inherit
with:
duckdb_version: v1.4.5
extension_name: erpl
exclude_archs: linux_arm64;windows_amd64_rtools;wasm_mvp;wasm_eh;wasm_threads;
# A deploy job depends on its build job, and `needs` normally requires that job
# to have succeeded outright. Because the build is a matrix over platforms, a
# single broken platform made the whole build job "failure" and skipped deploy
# for *every* platform. That is how a Windows-only outage (msys2 purging a pinned
# runtime, issue #115) silently stopped all publishing to get.erpl.io for ten
# days, across Linux and macOS too.
#
# `!cancelled()` lets deploy run when the build job did not succeed outright. The
# deploy job is itself a matrix over architectures and each leg downloads only its
# own artifact, so the platforms that built still publish. A platform whose build
# failed has no artifact, so its deploy leg fails at download — which is the
# honest signal, and keeps the broken platform visible in CI rather than hiding it.
duckdb-stable-deploy-v145:
name: Deploy extension binaries
needs: duckdb-stable-build-v145
if: ${{ !cancelled() }}
uses: ./.github/workflows/_extension_deploy.yml
secrets: inherit
with:
duckdb_version: v1.4.5
extension_name: erpl
exclude_archs: linux_arm64;windows_amd64_rtools;wasm_mvp;wasm_eh;wasm_threads;
deploy_latest: ${{ startsWith(github.ref, 'refs/tags/v') || github.ref == 'refs/heads/master' }}
deploy_versioned: ${{ !(startsWith(github.ref, 'refs/tags/v')) && !(github.ref == 'refs/heads/master') }}
duckdb-stable-build-v154:
name: Build v.1.5.5 extension binaries
uses: ./.github/workflows/_extension_build.yml
secrets: inherit
with:
duckdb_version: v1.5.5
extension_name: erpl
exclude_archs: linux_arm64;windows_amd64_rtools;wasm_mvp;wasm_eh;wasm_threads;
duckdb-stable-deploy-v154:
name: Deploy extension binaries
needs: duckdb-stable-build-v154
# See the note above duckdb-stable-deploy-v145.
if: ${{ !cancelled() }}
uses: ./.github/workflows/_extension_deploy.yml
secrets: inherit
with:
duckdb_version: v1.5.5
extension_name: erpl
exclude_archs: linux_arm64;windows_amd64_rtools;wasm_mvp;wasm_eh;wasm_threads;
deploy_latest: ${{ startsWith(github.ref, 'refs/tags/v') || github.ref == 'refs/heads/master' }}
deploy_versioned: ${{ !(startsWith(github.ref, 'refs/tags/v')) && !(github.ref == 'refs/heads/master') }}