fix(deps): update non-major - #21
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
renovate
Bot
force-pushed
the
renovate/non-major
branch
from
March 14, 2026 07:38
964209e to
ef68190
Compare
renovate
Bot
force-pushed
the
renovate/non-major
branch
from
April 15, 2026 12:53
ef68190 to
99aca3d
Compare
renovate
Bot
force-pushed
the
renovate/non-major
branch
2 times, most recently
from
May 12, 2026 07:50
3762a55 to
1018a21
Compare
renovate
Bot
force-pushed
the
renovate/non-major
branch
2 times, most recently
from
June 7, 2026 20:04
e9480b5 to
ccc2105
Compare
renovate
Bot
force-pushed
the
renovate/non-major
branch
from
July 11, 2026 20:13
ccc2105 to
9df9df3
Compare
renovate
Bot
force-pushed
the
renovate/non-major
branch
2 times, most recently
from
August 20, 2026 00:09
c28c5fe to
8d08a87
Compare
renovate
Bot
force-pushed
the
renovate/non-major
branch
from
August 23, 2026 20:02
8d08a87 to
e036c75
Compare
renovate
Bot
force-pushed
the
renovate/non-major
branch
from
September 5, 2026 20:15
e036c75 to
5f9644d
Compare
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
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.
This PR contains the following updates:
v1.5.1→v1.5.5v1.6.1→v1.12.11.13→1.27.1^1.13→^1.27.1Release Notes
go-chi/chi (github.com/go-chi/chi)
v1.5.5Compare Source
v1.5.4Compare Source
github.com/go-chi/chi/v5introduces the adoption of Go's SIV to adhere to the current state-of-the-tools in Go.The most responsible thing to do for everyone's benefit is to just release v5 with SIV, so I present to you all,
chi v5 at
github.com/go-chi/chi/v5. I hope someday the developer experience and ergonomics I've been seekingwill still come to fruition in some form, see golang/go#44550
v1.5.3Compare Source
v1.5.2Compare Source
stretchr/testify (github.com/stretchr/testify)
v1.12.1Compare Source
This is the first release which has the minimum dependencies practical in testify v1. The last remaining dependencies are github.com/stretchr/objx which itself has no dependencies, and go.yaml.in/yaml/v3. Removing objx would require v2, it cannot be vendored. Removing YAML would require vendoring the yaml library, which would do more harm than good. It's better to become aware of vulnerabilities in the official yaml package than to attempt to maintain our own.
What's Changed
go.yaml.in/yaml/v3by @harryzcy in #1935New Contributors
Full Changelog: stretchr/testify@v1.12.0...v1.12.1
What's Changed
go.yaml.in/yaml/v3by @harryzcy in #1935New Contributors
Full Changelog: stretchr/testify@v1.12.0...v1.12.1
v1.12.0Compare Source
What's Changed
Functional Changes
Fixes
Documentation, Build & CI
New Contributors
Full Changelog: stretchr/testify@v1.11.0...v1.12.0
What's Changed
New Contributors
Full Changelog: stretchr/testify@v1.11.0...v1.12.0
v1.11.1Compare Source
This release fixes #1785 introduced in v1.11.0 where expected argument values implementing the stringer interface (
String() string) with a method which mutates their value, when passed to mock.Mock.On (m.On("Method", <expected>).Return()) or actual argument values passed to mock.Mock.Called may no longer match one another where they previously did match. The behaviour prior to v1.11.0 where the stringer is always called is restored. Future testify releases may not call the stringer method at all in this case.What's Changed
Full Changelog: stretchr/testify@v1.11.0...v1.11.1
v1.11.0Compare Source
What's Changed
Functional Changes
v1.11.0 Includes a number of performance improvements.
Fixes
Documentation, Build & CI
New Contributors
Full Changelog: stretchr/testify@v1.10.0...v1.11.0
v1.10.0Compare Source
What's Changed
Functional Changes
Fixes
Documentation, Build & CI
New Contributors
Full Changelog: stretchr/testify@v1.9.0...v1.10.0
v1.9.0Compare Source
What's Changed
Calledby @aud10slave in #631NotImplementsand variants by @hslatman in #1385New Contributors
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate using a curated preset maintained by
. View repository job log here