chore(deps): bump vendored stretchr/testify to v1.11.1 - #43
Merged
8lecramm merged 1 commit intoAug 2, 2026
Merged
Conversation
Test-framework bump (test-only, no production/consensus code path). v1.11.1 pulls a couple of transitive deps not previously vendored: - bump github.com/davecgh/go-spew v1.1.0 -> v1.1.1 - add github.com/stretchr/objx v0.5.2 (require closure; only used by testify/mock, which DERO does not import) - add gopkg.in/yaml.v3 v3.0.1 (testify/assert uses it for YAML diff formatting; v1.11.1 switched from yaml.v2). Old yaml.v2 left in place (harmless dead vendor, still referenced by other vendored deps). All target `go <=1.17` (1.17), so this is a clean standalone prep PR. Verification: - Build: `go build ./...` green - `go test ./cryptography/bn256/` PASS - `go test ./walletapi/xswd/` FAILS — but reproduced identically on clean community-dev (pre-existing flaky/state-sensitive test: "should have 0 item(s), but has 1" on TestXSWDStop). NOT introduced by this bump.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Test-framework bump of
github.com/stretchr/testify(old → v1.11.1). Test-only — no production or consensus code path is touched. Part of the dependency-prep track ahead of a future Go toolchain bump (see #40, #41, #42).Transitive changes (all
go <=1.17)v1.11.1 pulls a couple of deps not previously vendored:
github.com/davecgh/go-spewv1.1.0 → v1.1.1github.com/stretchr/objxv0.5.2 added (require closure; only used bytestify/mock, which DERO does not import)gopkg.in/yaml.v3v3.0.1 added (testify/assert uses it for YAML diff formatting; v1.11.1 switched from yaml.v2). Oldyaml.v2is left in place (harmless dead vendor, still referenced by other vendored deps).Verification
go build ./...green (targetgo 1.17)go test ./cryptography/bn256/— PASSgo test ./walletapi/xswd/— FAILS, but reproduced identically on clean community-dev (pre-existing flaky/state-sensitive test: "should have 0 item(s), but has 1" onTestXSWDStop). The failure is independent of this bump — DERO production code is unchanged.Note
This is the heaviest of the prep bumps because testify v1.11.1 adds two transitive vendors (yaml.v3 + objx). It does not advance consensus or transport paths; it modernizes the test framework toward the Phase-0 target go.mod.
🤖 Generated with opencode