Skip to content

Conversation

@everpcpc
Copy link
Member

Summary

This PR refactors the bindings release process to avoid PyPI restrictions on publishing from reusable workflows.

Changes

  • Removed publish parameter and job from reusable workflows (bindings.python.yml and bindings.nodejs.yml)
  • Added dedicated bindings_python_publish and bindings_nodejs_publish jobs directly in release.yml
  • Reusable workflows now only handle check, build, and integration testing
  • Publishing logic is now executed in the main release workflow

Why

PyPI does not allow publishing from reusable workflows (workflow_call). By moving the publish steps to the main release workflow, we can successfully publish Python packages to PyPI while keeping the rest of the CI pipeline modular.

Testing

  • The workflow structure has been tested to ensure artifacts are properly passed between jobs
  • Publishing will be validated in the next release

- Remove publish parameter and job from reusable workflows
- Add dedicated publish jobs in release.yml for PyPI and npm
- This avoids PyPI restrictions on publishing from reusable workflows
@everpcpc everpcpc changed the title refactor: move bindings publish steps to release workflow ci: move bindings publish steps to release workflow Jan 16, 2026
@everpcpc everpcpc marked this pull request as ready for review January 16, 2026 10:50
@everpcpc everpcpc merged commit e0baaca into databendlabs:main Jan 16, 2026
40 checks passed
@everpcpc everpcpc deleted the anchorage-wzf5x49v branch January 16, 2026 11:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant