Skip to content

feat: build v1.5.2 after v1.5.1 succeeds and deploy both versions #21

feat: build v1.5.2 after v1.5.1 succeeds and deploy both versions

feat: build v1.5.2 after v1.5.1 succeeds and deploy both versions #21

#
# This workflow calls the main distribution pipeline from DuckDB to build, test and (optionally) release the extension
#
# To build against a different DuckDB version:
# 1. Create a branch (e.g. duckdb-v1.5.2)
# 2. Update DUCKDB_VERSION below and the @ref in 'uses:' to match
# 3. Update the duckdb submodule: cd duckdb && git checkout v1.5.2
# 4. Update extension-ci-tools submodule: cd extension-ci-tools && git checkout v1.5.2
# 5. Push and the CI will build against the new version
#
name: Main Extension Distribution Pipeline
on:
push:
pull_request:
workflow_dispatch:
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-v151-build:
name: Build extension binaries (v1.5.1)
uses: duckdb/extension-ci-tools/.github/workflows/_extension_distribution.yml@v1.5.1
with:
duckdb_version: v1.5.1
ci_tools_version: v1.5.1
extension_name: hortus_pipeline
duckdb-v152-build:
name: Build extension binaries (v1.5.2)
needs: duckdb-v151-build
uses: duckdb/extension-ci-tools/.github/workflows/_extension_distribution.yml@v1.5.1
with:
duckdb_version: v1.5.2
ci_tools_version: v1.5.1
extension_name: hortus_pipeline
code-quality-check:
name: Code Quality Check
uses: duckdb/extension-ci-tools/.github/workflows/_extension_code_quality.yml@v1.5.1
with:
duckdb_version: v1.5.1
ci_tools_version: v1.5.1
extension_name: hortus_pipeline
format_checks: 'format;tidy'