Skip to content

chore: update packaged upstream - #65

Merged
erikbpf-fleet-renovate[bot] merged 1 commit into
mainfrom
automated/package-update-v2
Nov 18, 2026
Merged

erikbpf-fleet-renovate[bot] merged 1 commit into
mainfrom
automated/package-update-v2

Conversation

@erikbpf-fleet-renovate

Copy link
Copy Markdown
Contributor

Package files generated by scripts/update-opencode-v2.sh.

Required pull-request checks own build and smoke validation.

@hackerman-cr

hackerman-cr Bot commented Nov 18, 2026

Copy link
Copy Markdown

Automated review — ErikBPF/opencode-flake — c28ea93

Reviewed c28ea93684e41eb00ec3cc4c942454e0f2b5945c against 6f6ab671975605772701bcf47ec15ef45db8a199.

Script-generated bump of the vendored V2 client from 2.3.0 to 2.3.2 in packages/opencode-v2/package.nix: the version let-binding and the fetchurl SRI hash, exactly the two lines scripts/update-opencode-v2.sh rewrites, with no other file touched. I re-downloaded @opencode/cli-linux-x64 2.3.2 from the npm registry, recomputed the sha512 SRI and it equals the new hash byte for byte, and the extracted binary reports opencode v2.3.2, which satisfies both versionCheckHook and the CI smoke grep. The bundle carries no repository review skills or contributor guidance, so I applied the general lenses (correctness, compatibility, tests, CI, PR hygiene). No new P1/P2 findings; the change is complete and internally consistent, and the remaining evidence is the required CI jobs, which were still pending when the bundle was captured.

No new P1/P2 findings at this head. No action requested.


Validation

  • Read meta.json and request.md; the bundle shipped zero base-pinned skills and zero docs, and the base tree has no AGENTS.md, CLAUDE.md, CONTRIBUTING.md or .ai/skills, so there was no repository review skill to route and I applied the general lenses and record that here.
  • Read reviews.json, review_comments.json and issue_comments.json (all empty) and repo-context.md; prior bumps of this same file (PR chore: bump opencode v2 to 2.2.7 #62, chore: update packaged upstream #63) followed the identical two-line pattern, so no existing finding was duplicated.
  • Compared diff.patch against the fetched base (6f6ab67) and head (c28ea93) commits of the public repository: the base-to-head diff is identical, touches only packages/opencode-v2/package.nix, and the blob ids match the diff index line (076ff45..d08ddfc).
  • Downloaded https://registry.npmjs.org/@opencode/cli-linux-x64/-/cli-linux-x64-2.3.2.tgz and recomputed the sha512 SRI locally; it is exactly the hash added by the diff.
  • Extracted the tarball binary and ran opencode --version, which prints opencode v2.3.2, matching the versionCheckHook expectation and the opencode v$version alternative in the CI smoke grep.
  • Checked readelf -d on the new binary: DT_NEEDED is still only glibc components (libc.so.6, libpthread.so.0, libdl.so.2, libm.so.6, ld-linux-x86-64.so.2), so the existing autoPatchelfHook inputs remain sufficient.
  • Read checks.txt: check and package-build are pending and secrets is pass; I did not infer any CI result from that.
  • Did not run the Nix build or nix flake check.

Limits

  • No independent Nix build; nix build .#opencode-v2 was not executed by this review.
  • CI at the head (check, package-build) was reported pending in checks.txt and was not executed or re-read after capture.
  • The SRI hash was verified by a direct tarball download rather than through fetchurl substitution, so Nix's own fixed-output check remains CI's to prove.
  • Upstream 2.3.1/2.3.2 release notes and behavioral changes were not reviewed; only the packaged artifact and its version string were checked.

Automated review. Findings are candidates for human confirmation. Hackerman approves only when it found no P1/P2 issues; it does not replace human review of design or intent.

@hackerman-cr hackerman-cr Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Automated review at c28ea93: no P1/P2 findings.

@erikbpf-fleet-renovate
erikbpf-fleet-renovate Bot merged commit 6160cf0 into main Nov 18, 2026
7 checks passed
@erikbpf-fleet-renovate
erikbpf-fleet-renovate Bot deleted the automated/package-update-v2 branch November 18, 2026 18:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant