Skip to content

build(deps): bump moby/go-archive to v0.3.0 in state/redis (Dependabot alert #45) - #59

Merged
ThomasK33 merged 1 commit into
mainfrom
deps/go-archive-0.3.0-state-redis
Aug 28, 2026
Merged

build(deps): bump moby/go-archive to v0.3.0 in state/redis (Dependabot alert #45)#59
ThomasK33 merged 1 commit into
mainfrom
deps/go-archive-0.3.0-state-redis

Conversation

@ThomasK33

Copy link
Copy Markdown
Member

Resolves Dependabot alert #45 (high, GHSA-hfg8-hc9c-6c3h): github.com/moby/go-archive — crafted tar archive can write outside the extraction directory. Transitive via testcontainers-go in state/redis/go.mod; first patched version is v0.3.0. This is the twin of #45 (the PR), which fixed the same advisory path in state/postgres. No Dependabot PR existed yet (weekly schedule), so this bump is authored directly.

Changes

Module Dependency Old New
state/redis github.com/moby/go-archive (indirect) v0.2.0 v0.3.0
state/redis github.com/moby/sys/user (indirect, pulled by go-archive) v0.4.0 v0.4.1

Plus go.sum true-ups in examples/slack-redis-state and examples/slack-postgres-state: the postgres example's graph hashes were left stale by the #45 merge (module graph references go-archive/sys-user via the sibling replace); per-module go mod tidy + go work sync run to fixpoint corrects both.

Validation

  • GOWORK=off go build ./... in state/redis, state/nats, state/postgres, and both affected examples — all externally resolvable
  • mise run vet — clean across all workspace modules
  • GOFLAGS=-race mise run test — exit 0, 0 failures (Testcontainers redis/postgres + embedded NATS included)
  • tidy/sync fixpoint: rerunning produces no diff; footprint is go.mod/go.sum files only

Generated with mux • Model: anthropic:claude-fable-5 • Thinking: xhigh

Resolves Dependabot alert #45 (GHSA-hfg8-hc9c-6c3h, high): crafted tar
archive can write outside the extraction directory. Transitive via
testcontainers-go; same fix as state/postgres in #45 (the PR).

Also trues up stale go-archive/sys-user hashes in the example go.sums.
@ThomasK33

Copy link
Copy Markdown
Member Author

@codex review

@ThomasK33

Copy link
Copy Markdown
Member Author

@codex security review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Breezy!

Reviewed commit: 792cdd5f53

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@chatgpt-codex-connector

Copy link
Copy Markdown

Security review completed. No security issues were found in this pull request.

Reviewed commit: 792cdd5f53

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@ThomasK33
ThomasK33 merged commit 7ff6082 into main Aug 28, 2026
1 check passed
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