This repository has been archived by the owner on Jul 14, 2024. It is now read-only.
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.2.0
->v0.3.0
v1.5.4
->v1.7.0
v2.0.0
->v2.1.0
v0.9.0
->v0.11.0
v1.13.0
->v1.18.2
v0.25.16
->v0.30.1
v0.25.16
->v0.30.1
v0.25.16
->v0.30.1
Release Notes
chi-middleware/logrus-logger (github.com/chi-middleware/logrus-logger)
v0.3.0
Compare Source
What's Changed
New Contributors
Full Changelog: chi-middleware/logrus-logger@v0.2.0...v0.3.0
fsnotify/fsnotify (github.com/fsnotify/fsnotify)
v1.7.0
Compare Source
This version of fsnotify needs Go 1.17.
Additions
illumos: add FEN backend to support illumos and Solaris. (#371)
all: add
NewBufferedWatcher()
to use a buffered channel, which can be useful in cases where you can't control the kernel buffer and receive a large number of events in bursts. (#550, #572)all: add
AddWith()
, which is identical toAdd()
but allows passing options. (#521)windows: allow setting the ReadDirectoryChangesW() buffer size with
fsnotify.WithBufferSize()
; the default of 64K is the highest value that works on all platforms and is enough for most purposes, but in some cases a highest buffer is needed. (#521)Changes and fixes
inotify: remove watcher if a watched path is renamed (#518)
After a rename the reported name wasn't updated, or even an empty string. Inotify doesn't provide any good facilities to update it, so just remove the watcher. This is already how it worked on kqueue and FEN.
On Windows this does work, and remains working.
windows: don't listen for file attribute changes (#520)
File attribute changes are sent as
FILE_ACTION_MODIFIED
by the Windows API, with no way to see if they're a file write or attribute change, so would show up as a fsnotify.Write event. This is never useful, and could result in many spurious Write events.windows: return
ErrEventOverflow
if the buffer is full (#525)Before it would merely return "short read", making it hard to detect this error.
kqueue: make sure events for all files are delivered properly when removing a watched directory (#526)
Previously they would get sent with
""
(empty string) or"."
as the path name.kqueue: don't emit spurious Create events for symbolic links (#524)
The link would get resolved but kqueue would "forget" it already saw the link itself, resulting on a Create for every Write event for the directory.
all: return
ErrClosed
onAdd()
when the watcher is closed (#516)other: add
Watcher.Errors
andWatcher.Events
to the no-opWatcher
inbackend_other.go
, making it easier to use on unsupported platforms such as WASM, AIX, etc. (#528)other: use the
backend_other.go
no-op if theappengine
build tag is set; Google AppEngine forbids usage of the unsafe package so the inotify backend won't compile there.v1.6.0
Compare Source
This version of fsnotify needs Go 1.16 (this was already the case since 1.5.1, but not documented). It also increases the minimum Linux version to 2.6.32.
Additions
all: add
Event.Has()
andOp.Has()
(#477)This makes checking events a lot easier; for example:
Becomes:
all: add cmd/fsnotify (#463)
A command-line utility for testing and some examples.
Changes and fixes
inotify: don't ignore events for files that don't exist (#260, #470)
Previously the inotify watcher would call
os.Lstat()
to check if a file still exists before emitting events.This was inconsistent with other platforms and resulted in inconsistent event reporting (e.g. when a file is quickly removed and re-created), and generally a source of confusion. It was added in 2013 to fix a memory leak that no longer exists.
all: return
ErrNonExistentWatch
whenRemove()
is called on a path that'snot watched (#460)
inotify: replace epoll() with non-blocking inotify (#434)
Non-blocking inotify was not generally available at the time this library was written in 2014, but now it is. As a result, the minimum Linux version is bumped from 2.6.27 to 2.6.32. This hugely simplifies the code and is faster.
kqueue: don't check for events every 100ms (#480)
The watcher would wake up every 100ms, even when there was nothing to do. Now it waits until there is something to do.
macos: retry opening files on EINTR (#475)
kqueue: skip unreadable files (#479)
kqueue requires a file descriptor for every file in a directory; this would fail if a file was unreadable by the current user. Now these files are simply skipped.
windows: fix renaming a watched directory if the parent is also watched (#370)
windows: increase buffer size from 4K to 64K (#485)
windows: close file handle on Remove() (#288)
kqueue: put pathname in the error if watching a file fails (#471)
inotify, windows: calling Close() more than once could race (#465)
kqueue: improve Close() performance (#233)
all: various documentation additions and clarifications.
matoous/go-nanoid (github.com/matoous/go-nanoid/v2)
v2.1.0
Compare Source
Last version of go-nanoid drops support for older Go versions. From now on we will maintain support for last 3 major versions (that is, right now the oldest supported version is v1.20). Other than that, a few small updates and dependency bumps, see changelog for more details.
What's Changed
New Contributors
Full Changelog: matoous/go-nanoid@v1.5.0...v2.1.0
onrik/logrus (github.com/onrik/logrus)
v0.11.0
Compare Source
v0.10.0
Compare Source
spf13/viper (github.com/spf13/viper)
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
Full Changelog: spf13/viper@v1.14.0...v1.15.0
v1.14.0
Compare Source
What's Changed
Enhancements 🚀
Breaking Changes 🛠
Dependency Updates ⬆️
Full Changelog: spf13/viper@v1.13.0...v1.14.0
kubernetes/api (k8s.io/api)
v0.30.1
Compare Source
v0.30.0
Compare Source
v0.29.5
Compare Source
v0.29.4
Compare Source
v0.29.3
Compare Source
v0.29.2
Compare Source
v0.29.1
Compare Source
v0.29.0
Compare Source
v0.28.10
Compare Source
v0.28.9
Compare Source
v0.28.8
Compare Source
v0.28.7
Compare Source
v0.28.6
Compare Source
v0.28.5
Compare Source
v0.28.4
Compare Source
v0.28.3
Compare Source
v0.28.2
Compare Source
v0.28.1
Compare Source
v0.28.0
Compare Source
v0.27.14
Compare Source
v0.27.13
Compare Source
v0.27.12
Compare Source
v0.27.11
Compare Source
v0.27.10
Compare Source
v0.27.9
Compare Source
v0.27.8
Compare Source
v0.27.7
Compare Source
v0.27.6
Compare Source
v0.27.5
Compare Source
v0.27.4
Compare Source
v0.27.3
Compare Source
v0.27.2
Compare Source
v0.27.1
Compare Source
v0.27.0
Compare Source
v0.26.15
Compare Source
v0.26.14
Compare Source
v0.26.13
Compare Source
v0.26.12
Compare Source
v0.26.11
Compare Source
v0.26.10
Compare Source
v0.26.9
Compare Source
v0.26.8
Compare Source
v0.26.7
Compare Source
v0.26.6
Compare Source
v0.26.5
Compare Source
v0.26.4
Compare Source
v0.26.3
Compare Source
v0.26.2
Compare Source
v0.26.1
Compare Source
v0.26.0
Compare Source
kubernetes/apimachinery (k8s.io/apimachinery)
v0.30.1
Compare Source
v0.30.0
Compare Source
v0.29.5
Compare Source
v0.29.4
Compare Source
v0.29.3
Compare Source
v0.29.2
Compare Source
v0.29.1
Compare Source
v0.29.0
Compare Source
v0.28.10
Compare Source
v0.28.9
Compare Source
v0.28.8
Compare Source
v0.28.7
Compare Source
v0.28.6
Compare Source
v0.28.5
Compare Source
v0.28.4
Compare Source
v0.28.3
Compare Source
v0.28.2
Compare Source
v0.28.1
Compare Source
v0.28.0
Compare Source
v0.27.14
Compare Source
v0.27.13
Compare Source
v0.27.12
Compare Source
v0.27.11
Compare Source
v0.27.10
Compare Source
v0.27.9
Compare Source
v0.27.8
Compare Source
v0.27.7
Compare Source
v0.27.6
Compare Source
v0.27.5
Compare Source
v0.27.4
Compare Source
v0.27.3
Compare Source
v0.27.2
Compare Source
v0.27.1
Compare Source
v0.27.0
Compare Source
v0.26.15
Compare Source
v0.26.14
Compare Source
v0.26.13
Compare Source
v0.26.12
Compare Source
v0.26.11
Compare Source
v0.26.10
Compare Source
v0.26.9
Compare Source
v0.26.8
Compare Source
[`
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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 has been generated by Renovate Bot.