fix(deps): update module github.com/fsnotify/fsnotify to v1.7.0

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
github.com/fsnotify/fsnotify	v1.6.0 -> v1.7.0

---

Release Notes

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 to Add() 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 on Add() when the watcher is closed (#​516)

• other: add Watcher.Errors and Watcher.Events to the no-op Watcher in backend_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 the appengine build tag is set; Google AppEngine forbids usage of the unsafe package so the inotify backend won't compile there.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[github-actions]

Stale pull request message

[forking-renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (v1.7.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.