chore(deps): Update go minor and patch #9267
Open
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:
v0.30.0
->v0.31.1
v1.3.1
->v1.7.1
v1.7.1
->v1.19.0
v0.31.0
->v0.32.0
701f63a
->7588d65
v0.33.0
->v0.34.0
v0.28.0
->v0.29.0
v0.27.0
->v0.28.0
v0.28.0
->v0.29.0
v1.36.1
->v1.36.2
Release Notes
getsentry/sentry-go (github.com/getsentry/sentry-go)
v0.31.1
: 0.31.1Compare Source
The Sentry SDK team is happy to announce the immediate availability of Sentry Go SDK v0.31.1.
Bug Fixes
sentry-go/logrus
(#950)v0.31.0
: 0.31.0Compare Source
Breaking Changes
Remove support for metrics. Read more about the end of the Metrics beta here. (#914)
Remove support for profiling. (#915)
Remove
Segment
field from theUser
struct. This field is no longer used in the Sentry product. (#928)Every integration is now a separate module, reducing the binary size and number of dependencies. Once you update
sentry-go
to latest version, you'll need togo get
the integration you want to use. For example, if you want to use theecho
integration, you'll need to rungo get github.com/getsentry/sentry-go/echo
(#919).Features
Add the ability to override
hub
incontext
for integrations that use custom context. (#931)Add
HubProvider
Hook forsentrylogrus
, enabling dynamic Sentry hub allocation for each log entry or goroutine. (#936)This change enhances compatibility with Sentry's recommendation of using separate hubs per goroutine. To ensure a separate Sentry hub for each goroutine, configure the
HubProvider
like this:Bug Fixes
HTTPTranport
to prevent goroutine leaks. (#894)Worker can be also closed by calling
Close()
method on theHTTPTransport
instance.Close
should be called afterFlush
and before terminating the program otherwise some events may be lost.Misc
spf13/cast (github.com/spf13/cast)
v1.7.1
Compare Source
What's Changed
New Contributors
Full Changelog: spf13/cast@v1.7.0...v1.7.1
v1.7.0
Compare Source
What's Changed
Full Changelog: spf13/cast@v1.6.0...v1.7.0
v1.6.0
Compare Source
What's Changed
Full Changelog: spf13/cast@v1.5.1...v1.6.0
v1.5.1
Compare Source
What's Changed
New Contributors
Full Changelog: spf13/cast@v1.5.0...v1.5.1
v1.5.0
Compare Source
json.Number
time.Weekday
andtime.Month
values10.0
before any int parsing.v1.4.1
Compare Source
v1.4.0
: Add ToTimeInDefaultLocation/ECompare Source
spf13/viper (github.com/spf13/viper)
v1.19.0
Compare Source
What's Changed
Bug Fixes 🐛
Dependency Updates ⬆️
Other Changes
New Contributors
Full Changelog: spf13/viper@v1.18.1...v1.19.0
v1.18.2
Compare Source
tl;dr Skip 1.18.0 and 1.18.1 and upgrade to this version instead.
This release fixes a regression that appears in rare circumstances when using
Unmarshal
orUnmarshalExact
to decode values onto pointers with multiple indirection (eg. pointer to a pointer, etc). The change was introduced in 1.18.0 as a means to resolve a long-standing bug when decoding environment variables to structs.The feature is now disabled by default and can be enabled using the
viper_bind_struct
build tag. It's also considered experimental at this point, so breaking changes may be introduced in the future.What's Changed
Bug Fixes 🐛
Full Changelog: spf13/viper@v1.18.1...v1.18.2
v1.18.1
Compare Source
What's Changed
Bug Fixes 🐛
Full Changelog: spf13/viper@v1.18.0...v1.18.1
v1.18.0
Compare Source
Major changes
Highlighting some of the changes for better visibility.
Please share your feedback in the Discussion forum. Thanks! ❤️
AutomaticEnv
works withUnmarshal
Previously, environment variables that weren't bound manually or had no defaults could not be mapped by
Unmarshal
. (The problem is explained in details in this issue: #761)#1429 introduced a solution that solves that issue.
What's Changed
Enhancements 🚀
Bug Fixes 🐛
Dependency Updates ⬆️
Other Changes
New Contributors
Full Changelog: spf13/viper@v1.17.0...v1.18.0
v1.17.0
Compare Source
Major changes
Highlighting some of the changes for better visibility.
Please share your feedback in the Discussion forum. Thanks! ❤️
Minimum Go version: 1.19
Viper now requires Go 1.19
This change ensures we can stay up to date with modern practices and dependencies.
log/slog
support [BREAKING]Viper v1.11.0 added an experimental
Logger
interface to allow custom implementations (besides jwalterweatherman).In addition, it also exposed an experimental
WithLogger
function allowing to set a custom logger.This release deprecates that interface in favor of log/slog released in Go 1.21.
To preserve backwards compatibility with older Go versions, prior to Go 1.21 Viper accepts a *golang.org/x/exp/slog.Logger.
The experimental flag is removed.
New finder implementation [BREAKING]
As of this release, Viper uses a new library to look for files, called locafero.
The new library is better covered by tests and has been built from scratch as a general purpose file finder library.
The implementation is experimental and is hidden behind a
finder
build tag.What's Changed
Exciting New Features 🎉
Enhancements 🚀
strings.Cut
by @scop in https://github.com/spf13/viper/pull/1650Breaking Changes 🛠
Dependency Updates ⬆️
Other Changes
New Contributors
Full Changelog: spf13/viper@v1.16.0...v1.17.0
v1.16.0
Compare Source
What's Changed
Enhancements 🚀
Bug Fixes 🐛
Dependency Updates ⬆️
Other Changes
New Contributors
Full Changelog: spf13/viper@v1.15.0...v1.16.0
v1.15.0
Compare Source
What's Changed
Exciting New Features 🎉
Enhancements 🚀
Breaking Changes 🛠
Dependency Updates ⬆️
New Contributors
Configuration
📅 Schedule: Branch creation - "on Wednesday" (UTC), Automerge - At any time (no schedule defined).
🚦 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 was generated by Mend Renovate. View the repository job log.