Skip to content

chore(deps): update project dependencies - #1026

Open
cpcloud wants to merge 3 commits into
micasa-dev:mainfrom
cpcloud:codex/abandoned-dependency-update
Open

chore(deps): update project dependencies#1026
cpcloud wants to merge 3 commits into
micasa-dev:mainfrom
cpcloud:codex/abandoned-dependency-update

Conversation

@cpcloud

@cpcloud cpcloud commented Aug 8, 2026

Copy link
Copy Markdown
Collaborator

What changed

  • Updated the full Go module graph together, including the abandoned SQLite, validator, x/sys, phonenumbers, and mcp-go updates.
  • Refreshed the Nix flake input and Go vendor hash so the packaged build uses the same dependency set.
  • Updated SHA-pinned GitHub Actions and supplied the cache keys required by Blacksmith builder v2.
  • Migrated the Biome rule configuration to its current schema.

Why

The separate dependency PRs stopped receiving Renovate updates after the vendor-hash workflow edited their branches. Updating the graph as one unit avoids combining individually stale lockfile states and lets API, lint, packaging, platform, and vulnerability compatibility be checked together.

Review notes

  • Harden Runner is intentionally pinned to v2.20.0. Version 2.20.1 implicitly permits single-label domains in block mode and does not expose a compatibility input, so taking it would weaken the existing egress policy.
  • No new Go module paths were introduced. The updated dependency sources and release changes were audited, including the SQLite/libc fixes.
  • The Blacksmith action update requires cache-key; each workflow uses the Dockerfile it builds.
  • The nixpkgs update builds prek's Rust vendor tree during Pre-commit, so only that job's block-mode allowlist adds static.crates.io:443.
  • Homebrew redirects macOS bottle downloads to GitHub's package-content host, so only the build/test job's block-mode allowlist adds pkg-containers.githubusercontent.com:443.

Supersedes #1021, #1018, #1009, #1004, and #1000.

Consolidate the stale per-module updates into one dependency set so Go modules, Nix vendoring, and pinned CI actions move together.

Keep Harden Runner at v2.20.0 because v2.20.1 implicitly permits single-label endpoints in block mode and exposes no compatibility input. Update Biome's rules configuration to the current preset schema so the updated toolchain remains warning-free.
@cpcloud cpcloud added ci CI/CD pipeline changes chore Maintenance and housekeeping nix Nix packaging and build dependencies labels Aug 8, 2026
cpcloud added 2 commits August 8, 2026 14:17
The updated nixpkgs input builds prek's Rust vendor tree during the pre-commit job. Harden Runner correctly blocked static.crates.io because that required source was absent from the job-specific allowlist.

Allow only the crates download endpoint for the pre-commit job while retaining block mode and the existing endpoint restrictions.
Homebrew redirects public bottle downloads from ghcr.io to GitHub's package-content host. Harden Runner blocked that unlisted endpoint, causing the macOS extraction-tool install to exhaust its retries before the build could start.

Allow only the documented HTTPS package-content endpoint in the build/test job so block-mode egress remains otherwise unchanged.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

chore Maintenance and housekeeping ci CI/CD pipeline changes dependencies nix Nix packaging and build

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant