After a long time, I created a PR into my CI/CD pipeline. A build of a new docker image (derived from official Meltano image) was triggered. I used Meltano 3.1, plugin versions had to be locked. Don't know why, but it started to fail with nasty errors. So, I decided to bump all versions to be up-to-date. Now I have Meltano 3.6 and all plugin lock files were updated. When I run

meltano install loader target-snowflake

, it fails. Example error snippet:

2025-01-13T16:01:15,381   psycopg/psycopgmodule.c:1091:25: error: lvalue required as left operand of assignment
2025-01-13T16:01:15,381    1091 |     Py_TYPE(&errorType) = &PyType_Type;
2025-01-13T16:01:15,382         |                         ^
2025-01-13T16:01:15,389   error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1

I tried Python 3.10, 3.11, and 3.12. Affected wheels which cannot be built: psycopg2, psycopg2-binary, cffi meltano.yaml:

- name: target-snowflake
    variant: meltanolabs
    pip_url: target-snowflake

Please, help.

Yeah, I can imagine the wise variant depends on old packages without wheels for modern platforms or Python versions

Btw the original motivation to bump everything was that tap-jira stopped working properly, it started to report that auth_token and email configuration properties are not set and are mandatory. I bumped the tap-jira and then the story of global bump started. However, the root cause for the original issue was that someone delivered a breaking change to tap-jira, replacing properties `username`/`password` with `email`/`api_token`. I quickly did a brief git blame and think you, @Edgar Ramírez (Arch.dev), know something about it, right? 😉

I quickly did a brief git blame and think you, @Edgar Ramírez (Arch.dev), know something about it, right?

yeah, I didn't push that but it was briefly discussed here: I quickly did a brief git blame and think you, @Edgar Ramírez (Arch.dev), know something about it, right?