Skip to content

Fix Strix protobuf dependency lock - #212

Merged
opencode-agent[bot] merged 6 commits into
mainfrom
fix-strix-protobuf-lock
Jun 30, 2026
Merged

opencode-agent[bot] merged 6 commits into
mainfrom
fix-strix-protobuf-lock

Conversation

@seonghobae

Copy link
Copy Markdown
Contributor

Fix the central Strix dependency lock so google-cloud-aiplatform==1.133.0 can install with its protobuf<7.0.0 constraint. Recent central Strix runs failed during pip resolution with protobuf==7.35.1 selected from the hash lock. This restores the last compatible protobuf==6.33.6 hash block.\n\nVerification:\n- py -3 -m py_compile scripts/ci/pr_review_merge_scheduler.py scripts/ci/opencode_review_normalize_output.py scripts/ci/noema_review_gate.py scripts/ci/render_opencode_prompt_template.py\n- py -3 -m pip install --dry-run --require-hashes -r requirements-strix-ci-hashes.txt passed the protobuf resolver conflict and stopped only on Windows-only pywin32 hash-mode behavior from docker; the failing central CI environment is Linux.

@seonghobae
seonghobae force-pushed the fix-strix-protobuf-lock branch from 8c25408 to 4f4831f Compare June 30, 2026 09:58
@opencode-agent

opencode-agent Bot commented Jun 30, 2026 •

Copy link
Copy Markdown
Contributor

OpenCode Review Overview

  • Head SHA: aeaade1f79adc907e08820372649f0c99890de84
  • Workflow run: 28440784567
  • Workflow attempt: 1
  • Gate result: APPROVE (approval step)

Pull request overview

OpenCode model attempts did not emit a usable current-head control block, but the deterministic approval fallback verified this is a no-diff or central review-process-only change with same-head peer checks green.

Findings

No blocking findings.

Changed-file evidence

  • no changed files; PR head tree is already represented in the base branch

Summary

Reviewed the bounded no-diff or central review process change list and peer GitHub Checks for current head aeaade1f79adc907e08820372649f0c99890de84. This fallback is limited to no-diff PR heads or the central OpenCode/Strix workflow and CI-gate files, after coverage evidence succeeded, peer checks completed without failures, mergeability was checked, and unresolved human review threads were absent.

Verification posture: Linter/static: peer GitHub Checks completed without source-backed failures before fallback approval. TDD/regression: central CI gate tests are part of the changed review-process files and peer checks completed. Coverage: Coverage execution evidence job result was success and completed before approval. Docstring coverage: Coverage evidence handled configured docstring gates or advisory status. DAG: Change Flow DAG maps central review workflow/script changes to required review checks and fallback approval path. PoC/execution: peer GitHub Checks and coverage evidence were re-queried for this exact head before approval. DDD/domain: no product domain code is in the fallback allowlist. CDD/context: structural scope is restricted to the central review process files listed above. Similar issues: repeated OPENCODE_REVIEW_UNAVAILABLE outcomes for this head motivated this fallback path. Claim/concept check: no PR metadata claims were accepted beyond GitHub diff and check APIs. Standards search: not applicable for this process-only fallback. Compatibility/convention: fallback reuses existing create_pull_review, check, mergeability, and human-thread gates. Breaking-change/backcompat: limited to central review workflow behavior. Performance: no runtime product path changed. Developer experience: maintainers get a review-state outcome instead of a silent tooling-stability dead end. User experience: PR readers get an explicit approval reason and changed-file evidence. Security/privacy: approval token and pull_request_target review boundaries remain unchanged.

  • Result: APPROVE
  • Reason: no-diff or central review-process-only fallback after repeated unusable OpenCode model output and green same-head peer evidence.
  • Head SHA: aeaade1f79adc907e08820372649f0c99890de84
  • Workflow run: 28440784567
  • Workflow attempt: 1

Change Flow DAG

flowchart LR
  Evidence["OpenCode evidence"] --> Review["Current PR review path"]
  Review --> Verify["Required checks"]
Loading

@seonghobae
seonghobae force-pushed the fix-strix-protobuf-lock branch from 4f4831f to e05da5f Compare June 30, 2026 10:01
@seonghobae
seonghobae force-pushed the fix-strix-protobuf-lock branch from e05da5f to 354d947 Compare June 30, 2026 10:12

@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 model attempts did not emit a usable current-head control block, so the approval gate used deterministic current-head evidence instead of model prose.

Findings

No blocking findings.

Summary

  • Result: APPROVE
  • Reason: coverage-evidence passed, peer GitHub Checks completed without failures, mergeability was clean, and no unresolved human review threads remained.
  • Deterministic evidence: current-head changed-file evidence (.github/workflows/opencode-review.yml, requirements-strix-ci-hashes.txt); coverage-evidence result success; peer checks from statusCheckRollup excluding this OpenCode check.
  • Model outcomes: primary=failed, fallback=failed, second_fallback=failed, catalog_fallback=failed.
  • Head SHA: 354d947e6780e11d886012a9fb7b249c7e7787a8
  • Workflow run: 28437479474
  • Workflow attempt: 1

Deterministic fallback approval was used only after model-output instability and did not bypass coverage, failed-check, mergeability, or human-review gates.

Change Flow DAG

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Workflow: opencode-review.yml"]
  S1 --> I1["GitHub Actions review job"]
  I1 --> R1["Review risk: Workflow: opencode-review.yml"]
  R1 --> V1["actionlint plus required checks"]
  Evidence --> S2["Changed file: requirements-strix-ci-hashes.txt"]
  S2 --> I2["repository behavior"]
  I2 --> R2["Review risk: Changed file: requirements-strix-ci-hashes.txt"]
  R2 --> V2["required checks"]
Loading

@opencode-agent
opencode-agent Bot enabled auto-merge (squash) June 30, 2026 10:38

@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 model attempts did not emit a usable current-head control block, so the approval gate used deterministic current-head evidence instead of model prose.

Findings

No blocking findings.

Summary

  • Result: APPROVE
  • Reason: coverage-evidence passed, peer GitHub Checks completed without failures, mergeability was clean, and no unresolved human review threads remained.
  • Deterministic evidence: current-head changed-file evidence (.github/workflows/opencode-review.yml, requirements-strix-ci-hashes.txt); coverage-evidence result success; peer checks from statusCheckRollup excluding this OpenCode check.
  • Model outcomes: primary=failed, fallback=failed, second_fallback=failed, catalog_fallback=failed.
  • Head SHA: 354d947e6780e11d886012a9fb7b249c7e7787a8
  • Workflow run: 28436837388
  • Workflow attempt: 3

Deterministic fallback approval was used only after model-output instability and did not bypass coverage, failed-check, mergeability, or human-review gates.

Change Flow DAG

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Workflow: opencode-review.yml"]
  S1 --> I1["GitHub Actions review job"]
  I1 --> R1["Review risk: Workflow: opencode-review.yml"]
  R1 --> V1["actionlint plus required checks"]
  Evidence --> S2["Changed file: requirements-strix-ci-hashes.txt"]
  S2 --> I2["repository behavior"]
  I2 --> R2["Review risk: Changed file: requirements-strix-ci-hashes.txt"]
  R2 --> V2["required checks"]
Loading

@opencode-agent
opencode-agent Bot disabled auto-merge June 30, 2026 10:56

@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 reviewed the current-head mergeability evidence and changed-file flow before approval, then found merge conflicts on the affected path.

Findings

1. HIGH Merge Conflict Guidance - Resolve the PR branch against the latest base branch

  • Problem: GitHub reports mergeStateStatus DIRTY for this pull request.
  • Root cause: Branch fix-strix-protobuf-lock cannot be merged cleanly into main; the changed-file flow below shows which review/runtime path is blocked by the conflict.
  • Fix: Merge or rebase the latest main into fix-strix-protobuf-lock, resolve conflict markers in the PR branch, rerun the focused checks, and push the same branch.
  • Repair commands:
gh pr checkout 212 --repo ContextualWisdomLab/.github
git fetch origin main
git merge --no-ff origin/main  # or: git rebase origin/main
git status --short
# resolve files, then git add <resolved-files>
# merge path: git commit
# rebase path: git rebase --continue
git push origin HEAD:fix-strix-protobuf-lock
# rebase path only: git push --force-with-lease origin HEAD:fix-strix-protobuf-lock
  • Regression test: Keep OpenCode approval gated on mergeability so model-output failures cannot approve a conflicted PR.

Change Flow DAG

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Workflow: opencode-review.yml"]
  S1 --> I1["GitHub Actions review job"]
  I1 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V1["actionlint plus required checks"]
Loading
  • Result: REQUEST_CHANGES
  • Reason: mergeStateStatus is DIRTY; mergeable is CONFLICTING.
  • Head SHA: 79d16150cd5b6fb431313615376c71b41301aac9
  • Workflow run: 28438962098
  • Workflow attempt: 1

@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 model attempts did not emit a usable current-head control block, but the deterministic approval fallback verified this is a no-diff or central review-process-only change with same-head peer checks green.

Findings

No blocking findings.

Changed-file evidence

  • no changed files; PR head tree is already represented in the base branch

Summary

Reviewed the bounded no-diff or central review process change list and peer GitHub Checks for current head aeaade1f79adc907e08820372649f0c99890de84. This fallback is limited to no-diff PR heads or the central OpenCode/Strix workflow and CI-gate files, after coverage evidence succeeded, peer checks completed without failures, mergeability was checked, and unresolved human review threads were absent.

Verification posture: Linter/static: peer GitHub Checks completed without source-backed failures before fallback approval. TDD/regression: central CI gate tests are part of the changed review-process files and peer checks completed. Coverage: Coverage execution evidence job result was success and completed before approval. Docstring coverage: Coverage evidence handled configured docstring gates or advisory status. DAG: Change Flow DAG maps central review workflow/script changes to required review checks and fallback approval path. PoC/execution: peer GitHub Checks and coverage evidence were re-queried for this exact head before approval. DDD/domain: no product domain code is in the fallback allowlist. CDD/context: structural scope is restricted to the central review process files listed above. Similar issues: repeated OPENCODE_REVIEW_UNAVAILABLE outcomes for this head motivated this fallback path. Claim/concept check: no PR metadata claims were accepted beyond GitHub diff and check APIs. Standards search: not applicable for this process-only fallback. Compatibility/convention: fallback reuses existing create_pull_review, check, mergeability, and human-thread gates. Breaking-change/backcompat: limited to central review workflow behavior. Performance: no runtime product path changed. Developer experience: maintainers get a review-state outcome instead of a silent tooling-stability dead end. User experience: PR readers get an explicit approval reason and changed-file evidence. Security/privacy: approval token and pull_request_target review boundaries remain unchanged.

  • Result: APPROVE
  • Reason: no-diff or central review-process-only fallback after repeated unusable OpenCode model output and green same-head peer evidence.
  • Head SHA: aeaade1f79adc907e08820372649f0c99890de84
  • Workflow run: 28440784567
  • Workflow attempt: 1

Change Flow DAG

flowchart LR
  Evidence["OpenCode evidence"] --> Review["Current PR review path"]
  Review --> Verify["Required checks"]
Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant