Bump version of this connector from 2.1.1 to 2.1.2 so the new release will be built with the apple m1 compatible psycopg-binary and will be published to PyPI.
Types of changes
What types of changes does your code introduce to PipelineWise?
[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)
Checklist
[x] Description above provides context of the change
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] Unit tests for changes (not needed for documentation changes)
[x] CI checks pass with my changes
[x] Bumping version in setup.py is an individual PR and not mixed with feature or bugfix PRs
[ ] Commit message/PR title starts with [AP-NNNN] (if applicable. AP-NNNN = JIRA ID)
[ ] Branch name starts with AP-NNN (if applicable. AP-NNN = JIRA ID)
Problem
The latest
2.1.1version of this connector on PyPI doesn't run on apple m1 processors, because the compatiblepsycopg2-binarywheels added at psycopg2-3.9.3. Psycopg has already been bumped in the main branch by https://github.com/transferwise/pipelinewise-target-postgres/pull/106 but the new build has not been released to PyPI: https://pypi.org/project/pipelinewise-target-postgres/Proposed changes
Bump version of this connector from
2.1.1to2.1.2so the new release will be built with the apple m1 compatiblepsycopg-binaryand will be published to PyPI.Types of changes
What types of changes does your code introduce to PipelineWise?
Checklist
setup.pyis an individual PR and not mixed with feature or bugfix PRs[AP-NNNN](if applicable. AP-NNNN = JIRA ID)AP-NNN(if applicable. AP-NNN = JIRA ID)