Skip to content

test: use main branch of python-bigquery and python-bigquery-storage for pre-release tests #857

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 21, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions noxfile.py
Original file line number Diff line number Diff line change
Expand Up @@ -324,8 +324,6 @@ def prerelease(session):
"--pre",
"--upgrade",
"google-api-core",
"google-cloud-bigquery",
"google-cloud-bigquery-storage",
"google-cloud-core",
"google-resumable-media",
# Exclude version 1.49.0rc1 which has a known issue. See https://github.com/grpc/grpc/pull/30642
Expand All @@ -344,6 +342,14 @@ def prerelease(session):
"pytest-cov",
)

# Install python-bigquery and python-bigquery-storage from main to detect
# any potential breaking changes. For context, see:
# https://github.com/googleapis/python-bigquery-pandas/issues/854
session.install(
"https://github.com/googleapis/python-bigquery/archive/main.zip",
"https://github.com/googleapis/python-bigquery-storage/archive/main.zip",
)

# Because we test minimum dependency versions on the minimum Python
# version, the first version we test with in the unit tests sessions has a
# constraints file containing all dependencies and extras.
Expand Down
Loading