Skip to content

Conversation

@kyungsoo-datahub
Copy link
Contributor

  • Add upper bounds to all dependencies using next major version (e.g., <3.0.0)
  • For 0.x packages, use tight bounds (<=current) or <1.0.0 where no 1.x exists
  • Add comments documenting automatic dependency chains:
    • ex> numpy<2 -> feast<=0.47 -> pyarrow<18.1 (resolved automatically)
  • Keep explicit constraints for deliberate choices (sqlalchemy<2, numpy<2)

@github-actions
Copy link
Contributor

github-actions bot commented Jan 6, 2026

Linear: ING-1334

@github-actions github-actions bot added the ingestion PR or Issue related to the ingestion of metadata label Jan 6, 2026
@codecov
Copy link

codecov bot commented Jan 6, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

@alwaysmeticulous
Copy link

alwaysmeticulous bot commented Jan 6, 2026

✅ Meticulous spotted 0 visual differences across 967 screens tested: view results.

Meticulous evaluated ~8 hours of user flows against your PR.

Expected differences? Click here. Last updated for commit 974146c. This comment will update as new commits are pushed.

@datahub-cyborg datahub-cyborg bot added the needs-review Label for PRs that need review from a maintainer. label Jan 6, 2026
@codecov
Copy link

codecov bot commented Jan 7, 2026

Bundle Report

Bundle size has no change ✅

"click>=7.1.2, !=8.2.0",
"click>=7.1.2,!=8.2.0,<9.0.0",
"click-default-group",
"PyYAML",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[MINOR] There are still unbounded packages, plan to upper-bound all the packages right ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done. Thanks.

# `aws_access_key_id`, `aws_secret_access_key`, and `aws_session_token` were deprecated and removed in version
# 0.8.0.
"pyiceberg[glue,hive,dynamodb,snappy,hive,s3fs,adlfs,pyarrow,zstandard]>=0.8.0",
"pyiceberg[glue,hive,dynamodb,snappy,hive,s3fs,adlfs,pyarrow,zstandard]>=0.8.0,<=0.10.0",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

pyiceberg is still actively developed - should we strict pin to the latest version ? same with databricks-sdk

Copy link
Contributor

@askumar27 askumar27 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Question: Do we need the lower bounds - would upper bound just suffice?

@datahub-cyborg datahub-cyborg bot added pending-submitter-response Issue/request has been reviewed but requires a response from the submitter needs-review Label for PRs that need review from a maintainer. and removed needs-review Label for PRs that need review from a maintainer. pending-submitter-response Issue/request has been reviewed but requires a response from the submitter labels Jan 7, 2026
…p.py

- Add upper bounds to all dependencies using next major version (e.g., <3.0.0)
- For 0.x packages, use tight bounds (<=current) or <1.0.0 where no 1.x exists
- Add comments documenting automatic dependency chains:
  - numpy<2 -> feast<=0.47 -> pyarrow<18.1 (resolved automatically)
  - sqlalchemy<2 -> sqlalchemy-pytds<1.0, sqlalchemy-hana<4.0 (resolved automatically)
  - protobuf<5 -> grpcio-tools<1.63 (resolved automatically)
  - urllib3<2 -> tableauserverclient<0.27 (resolved automatically)
- Keep explicit constraints for deliberate choices (sqlalchemy<2, numpy<2)
Add version upper bounds to packages that previously had no constraints.

Strategy:
- For 1.x+ packages: <next_major.0.0
- For 0.x packages: <0.{minor+1}.0
"excel": {
"openpyxl>=3.1.5",
"openpyxl>=3.1.5,<4.0.0",
"pandas",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let add a upper bound here as well

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added. Thanks.

@datahub-cyborg datahub-cyborg bot added pending-submitter-response Issue/request has been reviewed but requires a response from the submitter and removed needs-review Label for PRs that need review from a maintainer. labels Jan 15, 2026
…kages

Add version upper bounds to packages that were missed by the automated
script (packages with no existing version specifiers):
- google-cloud-bigquery<4.0.0
- google-cloud-resource-manager<2.0.0
- google-cloud-dataplex<3.0.0
- pandas<3.0.0 (excel plugin)
@datahub-cyborg datahub-cyborg bot added needs-review Label for PRs that need review from a maintainer. and removed pending-submitter-response Issue/request has been reviewed but requires a response from the submitter labels Jan 15, 2026
Copy link
Contributor

@askumar27 askumar27 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Notes from review meetings:

There are 4 types of py package bounding cases we have:

  1. With strict upper and lower bounds - these are untouched
  2. With lower bounds only (mainly the case) - upper bounds are added to the current latest MAJOR version - ensuring not to cause breaking changes
  3. With no bounds - upper bounds are added to the current latest MAJOR version - ensuring not to cause breaking changes
  4. With upper bounds only - these are untouched

@datahub-cyborg datahub-cyborg bot added pending-submitter-merge and removed needs-review Label for PRs that need review from a maintainer. labels Jan 15, 2026
@kyungsoo-datahub kyungsoo-datahub merged commit e86783d into master Jan 15, 2026
66 checks passed
@kyungsoo-datahub kyungsoo-datahub deleted the feat/metadata-ingestion-pin-versions branch January 15, 2026 21:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ingestion PR or Issue related to the ingestion of metadata pending-submitter-merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants