nuxencs / seasonpackarr

A companion app for autobrr that automagically hardlinks downloaded episodes to a season folder when a season pack is announced, eliminating the need for re-downloading existing episodes.
GNU General Public License v2.0
45 stars 3 forks source link

chore(deps): bump the golang group with 7 updates #27

Closed dependabot[bot] closed 9 months ago

dependabot[bot] commented 9 months ago

Bumps the golang group with 7 updates:

Package From To
github.com/autobrr/go-qbittorrent 1.3.3 1.7.1
github.com/fsnotify/fsnotify 1.6.0 1.7.0
github.com/go-chi/chi/v5 5.0.8 5.0.10
github.com/google/uuid 1.1.2 1.4.0
github.com/moistari/rls 0.5.9 0.5.10
github.com/rs/zerolog 1.30.0 1.31.0
github.com/spf13/viper 1.16.0 1.17.0

Updates github.com/autobrr/go-qbittorrent from 1.3.3 to 1.7.1

Commits


Updates github.com/fsnotify/fsnotify from 1.6.0 to 1.7.0

Release notes

Sourced from github.com/fsnotify/fsnotify's releases.

v1.7.0

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.

#371: fsnotify/fsnotify#371 #516: fsnotify/fsnotify#516 #518: fsnotify/fsnotify#518 #520: fsnotify/fsnotify#520 #521: fsnotify/fsnotify#521 #524: fsnotify/fsnotify#524 #525: fsnotify/fsnotify#525

... (truncated)

Changelog

Sourced from github.com/fsnotify/fsnotify's changelog.

1.7.0 - 2023-10-22

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)

... (truncated)

Commits
  • cfc9c4f Few more tiny doc fixes >_<
  • c3fa8e6 Proof-read some docs and prepare 1.7.0 release
  • 5310461 Remove stray trailing space in doc comment
  • f01d91e Add NewBufferedWatcher() (#572)
  • e545940 Merge pull request #589 from fsnotify/win-rm
  • c86f21c Document and test removing watched directory on Windows
  • 68111f2 Merge pull request #588 from fsnotify/illumos
  • 0614185 Add back illumos
  • 2f2332a Idiomatic bitwise operations
  • 769aaa7 Tweak docs
  • Additional commits viewable in compare view


Updates github.com/go-chi/chi/v5 from 5.0.8 to 5.0.10

Release notes

Sourced from github.com/go-chi/chi/v5's releases.

v5.0.10

Thank you to all contributors and reviewers :)

v5.0.9

Changelog

Sourced from github.com/go-chi/chi/v5's changelog.

v5.0.10 (2023-07-13)

v5.0.9 (2023-07-13)

Commits


Updates github.com/google/uuid from 1.1.2 to 1.4.0

Release notes

Sourced from github.com/google/uuid's releases.

v1.4.0

1.4.0 (2023-10-26)

Features

  • UUIDs slice type with Strings() convenience method (#133) (cd5fbbd)

Fixes

  • Clarify that Parse's job is to parse but not necessarily validate strings. (Documents current behavior)

v1.3.1

1.3.1 (2023-08-18)

Bug Fixes

  • Use .EqualFold() to parse urn prefixed UUIDs (#118) (574e687)

Add randomness pool mode for V4 UUID and NullUUID for SQL Scanners.

From Andrey Pechkurov:

Adds an optional randomness pool mode for Random (Version 4) UUID generation. The pool contains random bytes read from the random number generator on demand in batches. Enabling the pool may improve the UUID generation throughput significantly.

Since the pool is stored on the Go heap, this feature may be a bad fit for security sensitive applications. That's why it's implemented as an opt-in feature.

From Samuel Roth:

Added support for NullUUID

A NullUUID can be marked not valid (i.e., null) for use with JSON and the database/sql/driver.Scanner interfaces.

Add NewString()

This release introduces the NewString() function which is the equivalent of uuid.New().String().

Syntactic cleanup

There are no code changes. A missing period was add to a godoc comment and the linter was told to not complain that the results of hash.Write() are ignored (the function cannot fail)

Further error optimizations

Do not allocate memory for errors (it is only one word)

Optimize error reporting

Optimize length of time it takes to discover an input is bad by no longer using fmt.Errorf, which is quite slow. It now uses a custom error type that formats the string when the Error method is called rather than when generating the error.

Changelog

Sourced from github.com/google/uuid's changelog.

1.4.0 (2023-10-26)

Features

  • UUIDs slice type with Strings() convenience method (#133) (cd5fbbd)

Fixes

  • Clarify that Parse's job is to parse but not necessarily validate strings. (Documents current behavior)

1.3.1 (2023-08-18)

Bug Fixes

  • Use .EqualFold() to parse urn prefixed UUIDs (#118) (574e687)

Changelog

Commits
  • 8de8764 chore(master): release 1.4.0 (#134)
  • 7c22e97 Clarify the documentation of Parse to state its job is to parse, not validate...
  • cd5fbbd feat: UUIDs slice type with Strings() convenience method (#133)
  • 47f5b39 docs: fix a typo in CONTRIBUTING.md (#130)
  • 542ddab chore(tests): add Fuzz tests (#128)
  • 06716f6 chore(tests): Add json.Unmarshal test with empty value cases (#116)
  • b3cae7c chore(master): release 1.3.1 (#127)
  • 7b8f57c fix(ci): switch to release-please app (#126)
  • e69e468 chore(ci): configure release-please, update contrib (#122)
  • 97c970d chore(ci): add apidiff check for API compatibility (#123)
  • Additional commits viewable in compare view


Updates github.com/moistari/rls from 0.5.9 to 0.5.10

Commits


Updates github.com/rs/zerolog from 1.30.0 to 1.31.0

Commits


Updates github.com/spf13/viper from 1.16.0 to 1.17.0

Release notes

Sourced from github.com/spf13/viper's releases.

v1.17.0

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.

[!WARNING] WithLogger accepts an *slog.Logger from now on.

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.

[!WARNING] The io/fs based implementation (that used to be hidden behind a finder build tag) has been removed.

What's Changed

Exciting New Features 🎉

Enhancements 🚀

... (truncated)

Commits
  • f62f86a refactor: make use of strings.Cut
  • 94632fa chore: Use pip3 explicitly to install yamllint
  • 3f6cadc chore: Fix copy-paste error for yamllint target
  • 287507c docs: add set subset KV example
  • f1cb226 chore(deps): update crypt
  • c292b55 test: refactor asserts
  • 3d006fe refactor: replace interface{} with any
  • 8a6dc5d build(deps): bump github/codeql-action from 2.21.8 to 2.21.9
  • 96c5c00 chore: remove deprecated build tags
  • 44911d2 build(deps): bump github/codeql-action from 2.21.7 to 2.21.8
  • Additional commits viewable in compare view


Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions