Bump testify from 1.10.0 to 1.11.1#157
Merged
Merged
Conversation
Upgrade github.com/stretchr/testify from v1.10.0 to v1.11.1. This project only uses basic testify assertions (assert.Equal, assert.NoError, etc.) and does not use mock.Mock, so the v1.11.0 mock breaking change (reverted in v1.11.1) has no impact. Zero-risk dependency bump. Supersedes Dependabot PR #127. Created with assistance from Claude 🤖 <claude@anthropic.com> Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Christopher Collins <collins.christopher@gmail.com>
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
1 participant
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
github.com/stretchr/testifyfrom v1.10.0 to v1.11.1assert.Equal,assert.NoError, etc.) and does not usemock.MockBackground
v1.11.0 introduced a breaking change in mock argument matching (
IsTypebecame strict), but this was reverted in v1.11.1. Since srepd does not use mocks at all, neither version poses any risk.Verification
go test ./...-- all tests passgo vet ./...-- cleanmake fmt-check-- cleanmake test-- all 4 test packages greendocs/plans/016-bump-testify.mdCo-Authored-By: Claude Opus 4.6 (1M context) noreply@anthropic.com