Skip to content

chore(deps): bump google-cloud-bigquery from 3.42.2 to 3.43.0 - #915

Closed
dependabot[bot] wants to merge 3 commits into
mainfrom
dependabot/pip/main/google-cloud-bigquery-3.43.0
Closed

chore(deps): bump google-cloud-bigquery from 3.42.2 to 3.43.0#915
dependabot[bot] wants to merge 3 commits into
mainfrom
dependabot/pip/main/google-cloud-bigquery-3.43.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 10, 2026

Copy link
Copy Markdown
Contributor

Bumps google-cloud-bigquery from 3.42.2 to 3.43.0.

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot
chore(deps): bump google-cloud-bigquery from 3.42.2 to 3.43.0
69a7400 
Bumps [google-cloud-bigquery](https://github.com/googleapis/python-bigquery) from 3.42.2 to 3.43.0.
- [Release notes](https://github.com/googleapis/python-bigquery/releases)
- [Changelog](https://github.com/googleapis/python-bigquery/blob/main/CHANGELOG.md)
- [Commits](https://github.com/googleapis/python-bigquery/commits)

---
updated-dependencies:
- dependency-name: google-cloud-bigquery
  dependency-version: 3.43.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python Pull requests that update python code labels Aug 10, 2026
@dependabot
dependabot Bot requested a review from seonghobae as a code owner August 10, 2026 13:36
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python Pull requests that update python code labels Aug 10, 2026
@seonghobae
seonghobae marked this pull request as draft August 11, 2026 07:01
@seonghobae ChatGPT Codex Connector

seonghobae commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Exact-head fail-closed RCA for 69a7400af0fe1aa5b6f39ae7c85971b422379488 against independently resolved live main 6eb06cdd08c79a06f7b390069d4ffa49e2eb7dba:

  • This PR changes only requirements-strix-ci-hashes.txt, the hash lock consumed by Strix automation.
  • The protected-main Strix Changed Path Quality CI pull-request path list omits that lock, so no exact-head Strix quality run exists. Generic security/supply-chain successes do not substitute for the missing consuming boundary.
  • Immediate cause: incomplete trigger coverage. Technical root cause: the executable dependency contract and its quality trigger are not co-owned. Control cause: dependency leaves can appear gate-clean without exercising the consumer.
  • The PR is Draft until an authoritative path-filter repair reaches protected main and a refreshed exact head produces terminal-success Strix quality evidence.
  • Central repair is writer-conflicted this invocation: open PRs fix(coverage): retry transient trusted uv downloads #790 and fix(coverage): replace stale LLVM runtime-boundary repair #827 both modify .github/workflows/strix-changed-path-quality-ci.yml. This loop will not create a third competing writer or weaken gates.

@seonghobae
seonghobae marked this pull request as ready for review August 12, 2026 04:09
@seonghobae ChatGPT Codex Connector

seonghobae commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

@opencode-agent review

Review exact current head 69a7400af0fe1aa5b6f39ae7c85971b422379488 against independently resolved live main 6eb06cdd08c79a06f7b390069d4ffa49e2eb7dba. 16 exact-head hosted workflows are terminal-success and no review thread is unresolved. Verify the google-cloud-bigquery dependency update is limited to the declared version and lock evidence, with no API, credential, or runtime-policy regression. Automated judgment is not qualifying independent human approval or merge authorization.

seonghobae
seonghobae reviewed Aug 12, 2026
View reviewed changes

@seonghobae seonghobae left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Exact-head dependency review: the one-file diff only changes google-cloud-bigquery and its two hashes in requirements-strix-ci-hashes.txt, and the observed generic workflows are successful. The exact head has no Strix Changed Path Quality result because the permanent manifest trigger is missing. #935 is the bounded prerequisite. After it reaches main, recreate or rebase this branch so Strix runs on the resulting exact head; then reacquire review and protection evidence. Approval and auto-merge are withheld until that evidence exists.

@seonghobae ChatGPT Codex Connector

seonghobae commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Exact-head gate status for 69a7400af0fe1aa5b6f39ae7c85971b422379488: this PR changes only requirements-strix-ci-hashes.txt. Generic security/supply-chain checks cannot validate that the regenerated complete Strix environment still installs and runs under the trusted hash-locked workflow.

Do not approve or merge until #935 is protected-merged (or equivalent permanent trigger behavior exists), this branch is rebased/recreated if required, and the resulting exact head passes the full Strix dependency-lock/import/model-pool/syntax/clean-worktree quality contract. Any head change invalidates prior evidence.

@seonghobae
seonghobae enabled auto-merge (squash) August 13, 2026 04:32
@seonghobae
test(strix): pin google-cloud-bigquery 3.43.0 hashes
9de47ea 
CWE-494/CWE-829: the Strix --require-hashes lock must keep both
published SHA-256 digests and must not retain 3.42.2.
@seonghobae
fix(coverage): accept only bounded relative requirement includes
abc78b1 
Materialize a base Python lock only when every package line is an exact
SHA-256 pin or a two-token relative -r/--requirement include of a
candidate lock path. A lone --require-hashes directive, ./dotted paths,
and -r other-hashes.txt no longer enter the trusted build context.
@seonghobae

seonghobae commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

@opencode-agent review

Re-evaluate exact current head abc78b1bf5cfd21ee30d176e9fe565630d2cad2d. 리뷰 확인 for the bounded-include increment; do not treat Checks wait as a blocker.

opencode-agent[bot]
opencode-agent Bot requested changes Aug 14, 2026
View reviewed changes

@opencode-agent opencode-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

OpenCode could not approve from deterministic current-head evidence because GitHub Checks have failed.

Findings

1. HIGH Current-head GitHub Checks - Fix failed required checks before approval

  • Problem: Failed same-head checks remain for abc78b1bf5cfd21ee30d176e9fe565630d2cad2d.
  • Root cause: The model-unavailable evidence fallback is allowed only when peer GitHub Checks are complete and clean.
  • Fix: Read and fix the failed check logs below, then rerun the current-head checks.
  • Regression test: Keep the model-unavailable fallback gated on an empty failed-check rollup.

Failed checks:

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file (5 files)"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file (5 files)"]
  R1 --> V1["required checks"]
  Evidence --> S2["Docs: strix-google-cloud-bigquery-pin.md"]
  S2 --> I2["operator or user guidance"]
  I2 --> R2["Review risk: Docs: strix-google-cloud-bigquery-pin.md"]
  R2 --> V2["docs review"]
  Evidence --> S3["CI script: materialize_base_python_requirements.py"]
  S3 --> I3["review and security gate shell path"]
  I3 --> R3["Review risk: CI script: materialize_base_python_requirements.py"]
  R3 --> V3["bash -n plus Strix self-test"]
  Evidence --> S4["Test (2 files)"]
  S4 --> I4["regression suite"]
  I4 --> R4["Review risk: Test (2 files)"]
  R4 --> V4["targeted test run"]
Loading

@opencode-agent

opencode-agent Bot commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

OpenCode Review Overview

  • Head SHA: abc78b1bf5cfd21ee30d176e9fe565630d2cad2d
  • Workflow run: 31754625356
  • Workflow attempt: 1
  • Gate result: REQUEST_CHANGES (approval step)

Pull request overview

OpenCode could not approve from deterministic current-head evidence because GitHub Checks have failed.

Findings

1. HIGH Current-head GitHub Checks - Fix failed required checks before approval

  • Problem: Failed same-head checks remain for abc78b1bf5cfd21ee30d176e9fe565630d2cad2d.
  • Root cause: The model-unavailable evidence fallback is allowed only when peer GitHub Checks are complete and clean.
  • Fix: Read and fix the failed check logs below, then rerun the current-head checks.
  • Regression test: Keep the model-unavailable fallback gated on an empty failed-check rollup.

Failed checks:

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file (5 files)"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file (5 files)"]
  R1 --> V1["required checks"]
  Evidence --> S2["Docs: strix-google-cloud-bigquery-pin.md"]
  S2 --> I2["operator or user guidance"]
  I2 --> R2["Review risk: Docs: strix-google-cloud-bigquery-pin.md"]
  R2 --> V2["docs review"]
  Evidence --> S3["CI script: materialize_base_python_requirements.py"]
  S3 --> I3["review and security gate shell path"]
  I3 --> R3["Review risk: CI script: materialize_base_python_requirements.py"]
  R3 --> V3["bash -n plus Strix self-test"]
  Evidence --> S4["Test (2 files)"]
  S4 --> I4["regression suite"]
  I4 --> R4["Review risk: Test (2 files)"]
  R4 --> V4["targeted test run"]
Loading

@opencode-agent
opencode-agent Bot disabled auto-merge August 14, 2026 01:54
@seonghobae
seonghobae marked this pull request as draft August 14, 2026 08:51
@seonghobae ChatGPT Codex Connector

seonghobae commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

Returned to Draft because this is no longer a clean Dependabot update.

The intended slice is the google-cloud-bigquery 3.42.2→3.43.0 pin/hash refresh with its focused Strix compatibility contract. Head abc78b1bf5cfd21ee30d176e9fe565630d2cad2d also carries unrelated trusted-uv materializer source/tests and broad governance-document changes, obscuring the actual supply-chain delta.

Recreate or rebuild from protected main so the effective diff contains only requirements-strix-ci-hashes.txt, the focused BigQuery pin regression, and directly attributable doctoring/changelog evidence. Preserve materializer work in its authoritative PR, then rerun exact-head Strix/security/supply-chain checks and obtain independent review.

@seonghobae ChatGPT Codex Connector

seonghobae commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

Closing this current branch rather than merging an overlapping dependency update. The intended google-cloud-bigquery refresh can be regenerated later, but this branch also carries trusted-uv materializer source/tests and central governance documentation that overlap #790's actively verified security repair. Recreate from protected main after #790 and #935 integrate, keep the next branch dependency-focused, and reacquire exact-head Strix/security/review evidence. No ignore rule or downgrade is introduced.

@seonghobae seonghobae closed this Aug 14, 2026
@dependabot @github

dependabot Bot commented on behalf of github Aug 14, 2026

Copy link
Copy Markdown
Contributor Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot
dependabot Bot deleted the dependabot/pip/main/google-cloud-bigquery-3.43.0 branch August 14, 2026 13:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@seonghobae seonghobae seonghobae left review comments
@opencode-agent opencode-agent[bot] opencode-agent[bot] requested changes

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file python Pull requests that update python code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@seonghobae