[Snyk] Security upgrade idna from 2.10 to 3.7

[deargvp1]

Snyk has created this PR to fix 1 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

• composer/workflows/requirements-composer.txt

⚠️ Warning

pandas-gbq 0.21.0 has requirement google-api-core<3.0.0dev,>=2.10.2, but you have google-api-core 1.34.1.
pandas-gbq 0.21.0 has requirement google-auth>=2.13.0, but you have google-auth 1.35.0.
opentelemetry-api 1.22.0 has requirement importlib-metadata<7.0,>=6.0, but you have importlib-metadata 2.1.3.
google-cloud-workflows 1.20.0 has requirement google-auth!=2.24.0,!=2.25.0,<3.0.0,>=2.14.1, but you have google-auth 1.35.0.
google-cloud-vision 1.0.2 has requirement protobuf<4.0.0dev, but you have protobuf 4.24.4.
google-cloud-videointelligence 1.16.3 has requirement protobuf<4.0.0dev, but you have protobuf 4.24.4.
google-cloud-translate 1.7.2 has requirement protobuf<4.0.0dev, but you have protobuf 4.24.4.
google-cloud-texttospeech 1.0.3 has requirement protobuf<4.0.0dev, but you have protobuf 4.24.4.
google-cloud-tasks 2.21.0 has requirement google-auth!=2.24.0,!=2.25.0,<3.0.0,>=2.14.1, but you have google-auth 1.35.0.
google-cloud-speech 1.3.4 has requirement protobuf<4.0.0dev, but you have protobuf 4.24.4.
google-cloud-spanner 1.19.3 has requirement protobuf<4.0.0dev, but you have protobuf 4.24.4.
google-cloud-spanner 1.19.3 has requirement grpc-google-iam-v1<0.13dev,>=0.12.3, but you have grpc-google-iam-v1 0.14.3.
google-cloud-secret-manager 1.0.2 has requirement grpc-google-iam-v1<0.13dev,>=0.12.3, but you have grpc-google-iam-v1 0.14.3.
google-cloud-secret-manager 1.0.2 has requirement protobuf<4.0.0dev, but you have protobuf 4.24.4.
google-cloud-redis 2.20.0 has requirement google-auth!=2.24.0,!=2.25.0,<3.0.0,>=2.14.1, but you have google-auth 1.35.0.
google-cloud-pubsub 2.34.0 has requirement google-auth<3.0.0,>=2.14.1, but you have google-auth 1.35.0.
google-cloud-os-login 2.19.0 has requirement google-auth!=2.24.0,!=2.25.0,<3.0.0,>=2.14.1, but you have google-auth 1.35.0.
google-cloud-monitoring 2.29.1 has requirement google-auth!=2.24.0,!=2.25.0,<3.0.0,>=2.14.1, but you have google-auth 1.35.0.
google-cloud-memcache 1.14.0 has requirement google-auth!=2.24.0,!=2.25.0,<3.0.0,>=2.14.1, but you have google-auth 1.35.0.
google-cloud-logging 2.7.2 has requirement grpc-google-iam-v1<0.13dev,>=0.12.3, but you have grpc-google-iam-v1 0.14.3.
google-cloud-logging 2.7.2 has requirement protobuf<4.0.0dev, but you have protobuf 4.24.4.
google-cloud-language 1.3.2 has requirement protobuf<4.0.0dev, but you have protobuf 4.24.4.
google-cloud-kms 2.24.2 has requirement google-auth!=2.24.0,!=2.25.0,<3.0.0dev,>=2.14.1, but you have google-auth 1.35.0.
google-cloud-dlp 1.0.2 has requirement protobuf<4.0.0dev, but you have protobuf 4.24.4.
google-cloud-dataproc 2.6.2 has requirement packaging<22.0.0dev,>=14.3, but you have packaging 24.0.
google-cloud-dataproc 2.6.2 has requirement protobuf<4.0.0dev, but you have protobuf 4.24.4.
google-cloud-datacatalog 3.29.0 has requirement google-auth!=2.24.0,!=2.25.0,<3.0.0,>=2.14.1, but you have google-auth 1.35.0.
google-cloud-container 1.0.3 has requirement grpc-google-iam-v1<0.13dev,>=0.12.3, but you have grpc-google-iam-v1 0.14.3.
google-cloud-container 1.0.3 has requirement protobuf<4.0.0dev, but you have protobuf 4.24.4.
google-cloud-bigtable 1.7.3 has requirement protobuf<4.0.0dev, but you have protobuf 4.24.4.
google-cloud-bigtable 1.7.3 has requirement grpc-google-iam-v1<0.13dev,>=0.12.3, but you have grpc-google-iam-v1 0.14.3.
google-cloud-bigquery 3.30.0 has requirement google-api-core[grpc]<3.0.0dev,>=2.11.1, but you have google-api-core 1.34.1.
google-cloud-bigquery 3.30.0 has requirement google-auth<3.0.0dev,>=2.14.1, but you have google-auth 1.35.0.
google-cloud-bigquery-storage 2.36.2 has requirement google-auth!=2.24.0,!=2.25.0,<3.0.0,>=2.14.1, but you have google-auth 1.35.0.
google-cloud-bigquery-datatransfer 3.21.0 has requirement google-auth!=2.24.0,!=2.25.0,<3.0.0,>=2.14.1, but you have google-auth 1.35.0.
google-cloud-automl 2.18.1 has requirement google-auth!=2.24.0,!=2.25.0,<3.0.0,>=2.14.1, but you have google-auth 1.35.0.
google-cloud-appengine-logging 1.8.0 has requirement google-auth!=2.24.0,!=2.25.0,<3.0.0,>=2.14.1, but you have google-auth 1.35.0.
google-auth-oauthlib 0.8.0 has requirement google-auth>=2.15.0, but you have google-auth 1.35.0.
google-api-core 1.34.1 has requirement protobuf!=3.20.0,!=3.20.1,!=4.21.0,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<4.0.0dev,>=3.19.5, but you have protobuf 4.24.4.
google-ads 7.0.0 has requirement protobuf<4.0.0,>=3.13.0, but you have protobuf 4.24.4.
Flask 1.1.4 has requirement itsdangerous<2.0,>=0.24, but you have itsdangerous 2.1.2.
Flask-JWT-Extended 3.25.1 has requirement PyJWT<2.0,>=1.6.4, but you have PyJWT 2.8.0.
Flask-AppBuilder 2.3.4 has requirement marshmallow<3.0.0,>=2.18.0, but you have marshmallow 3.19.0.
Flask-AppBuilder 2.3.4 has requirement email-validator<2,>=1.0.5, but you have email-validator 2.1.0.
apache-airflow 1.10.15 requires thrift, which is not installed.
apache-airflow 1.10.15 has requirement requests<2.24.0,>=2.20.0; python_version >= "3.0", but you have requests 2.31.0.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.
• Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Resource Exhaustion

---

Summary by cubic

Pins idna to 3.7+ to fix a known vulnerability and ensure a secure version is used by transitive dependencies. Adds an explicit requirement in composer/workflows/requirements-composer.txt.

• Dependencies
  • Added idna>=3.7 to composer/workflows/requirements-composer.txt to address SNYK-PYTHON-IDNA-6597975.

^{Written for commit c760c6e. Summary will update on new commits.}

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 7a099492-1d34-47ec-a9a5-c550175f7cdc

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch snyk-fix-8ab47753f71a51bfb477140f3352e6ea

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This pull request updates the composer/workflows/requirements-composer.txt file to pin the idna package to version 3.7 or higher, addressing a vulnerability identified by Snyk. There are no review comments, and I have no additional feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[cubic-dev-ai]

No issues found across 1 file

_{Re-trigger cubic}