Bump github.com/amatsagu/tempest from 1.7.2 to 1.9.4

[dependabot]

Bumps github.com/amatsagu/tempest from 1.7.2 to 1.9.4.

Release notes

Sourced from github.com/amatsagu/tempest's releases.

v1.9.4

Quick hotfix to add missing fields needed to resolve channel/role/user IDs from Modal Interaction.

Full Changelog: amatsagu/tempest@v1.9.3...v1.9.4

v1.9.3

What's Changed

• Added ability to filter file types users can upload to /slash commands or modal (using FileUploadComponent) in amatsagu/tempest#66.
• Slightly improved memory usage / memory allocation efficiency by taking advantage of struct field alignment in amatsagu/tempest#67.
• Bumped required Go version to 1.26.4.

Full Changelog: amatsagu/tempest@v1.9.2...v1.9.3

v1.9.2

Hotfix for v1.9.1. Updated logic of rate limiter to better handle batch requests. It was "stress tested" for 3 hours in a row and had no issues.

v1.9.1

Hotfix for v1.9.0. I've got reports from (2) larger bot developers that at scale - they got temporarily blocked by Discord's CloudFlare anti DDoS after sending ~15k requests in less than 10min. This appear to be a bug with handling retryable (mostly 429 error) requests. At large scale, bot may have dozens of ticking retryable requests and previously they were incorrectly handled (partially outside rate limit checks). This hotfix introduces:

• Fixes to original issue by adding missing checks and adding extra time sleep (for network backoff).
• Adds internal retryable requester counter - it will fail early & send error if REST Client detects suspicious amount of failed but retryable requests (there's a chance they happen due to Tempest bug but they also may be because of bad code or network issues).

v1.9.0

[!NOTE] This release would normally be versioned as v1.8.1, but it was promoted to v1.9.0 due to the possibility that the new API rate limiter could introduce breaking changes to some API calls.

What's Changed

• Upgraded REST implementation so now it also handles regional (per /endpoint) rate limit buckets. It uses by default quite aggressive settings for performance reasons but everything is configurable. Rate limiter can be disabled by providing custom http transport into http client used by REST Client. By default it may look like Tempest again consumes more memory - don't panic! It only sweeps old bucket data at specific thresholds to avoid spam of sweeping events. Example of it working:

• Improved documentation of various components, structs and examples by @​Bertie690 in amatsagu/tempest#62
• Added formatting/linting pre-commit hooks with Lefthook & golangci-lint by @​Bertie690 in amatsagu/tempest#65
• Fixed grammar typos in README + moved info about how to contribute into dedicated CONTRIBUTING.md by @​Bertie690 in amatsagu/tempest#64

Full Changelog: amatsagu/tempest@v1.8.0...v1.9.0

v1.8.0

What's Changed

• Added optional support for zlib-stream compression for GatewayClient (works only for incoming payloads over ws conn to gateway). It can reduce size of incoming requests by up to ~70% at cost of slightly higher CPU usage.
• Fixed potential race condition in Shard/Socket logic where (at least in theory) Shard logic could crash when trying to close and read/write from different goroutines in nearly the same time (max ~4ns time window).
• Added missing status fields from presence update event payload. It now allows Tempest powered Discord Applicattions to display custom status.

Full Changelog: amatsagu/tempest@v1.7.2...v1.8.0

Commits

• 61f984b feat: retire one of the quality badges
• ef94b5f fix: add missing fields that were needed to use Select Components in Modals
• 472bd22 style: fix gofmt warnings
• 0299a6f feat: improve field alignment for all structs (#67)
• e5e0d55 feat: allow filtering file types in file upload modals and command option (#66)
• e8ceb17 feat: bump required go version
• 832f167 feat: optimize structs using automatic field alignment tool
• 75665b6 feat: allow filtering file types in file upload modals and attachment command...
• b4adae3 fix: delete example/example-bot binary
• 59c9d8d fix: implement strict bucket synchronization to prevent 429 spam
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)