Bump github.com/amatsagu/tempest from 1.3.4 to 1.4.4

[dependabot]

Bumps github.com/amatsagu/tempest from 1.3.4 to 1.4.4.

Release notes

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

v1.4.4

What's Changed

• Added on ready callback for shard manager when on Start() (used by GatewayClient). It allows to precisely run function when application is fully initialized - all shards are online.
• Improved ShardManager helper methods to fetch shard(s) status & ping value. Replaced ShardManager.ShardLatencies() with ShardManager.AllShardDetails() and added ShardManager.ShardDetails() for specific shard data.

Full Changelog: amatsagu/tempest@v1.4.3...v1.4.4

v1.4.3

Hotfix for v1.4.2. Added the missing Guild methods improvements that were accidentally left out of the last tag.

v1.4.2

What's Changed

• Removed deprecated Message.Interaction field. Replaced it with new Message.InteractionMetadata.
• Split HTTP & Gateway Clients in interaction so they can now be easily accessed. Additionally interactions now hold copy of pointer to BaseClient to optimize for hot paths (prefer CPU optimizations over memory usage).
• Added methods to safely delete handlers for static components or modals in BaseClient. This change now theoretically allows to create own dynamic handlers, control creation & destruction process if default dynamic handler is not ideal in some use cases.
• Added SharedMap.ReadRange() for efficient reading of all entries within single mutex lock.
• Optimized interaction & mentionable struct methods to use pointer instead using shallow copy. This should theoretically reduce memory usage on highly active Discord Applications (possibly may reduce CPU usage as well but it's difficult to prove).
• Optimized interaction methods hot paths to call values directly whenever possible.
• HTTPClient no longer shallow copies itself when creating interaction responder.

Full Changelog: amatsagu/tempest@v1.4.1...v1.4.2

v1.4.1

What's Changed

• Fixed bug that caused panic when using auto complete command handler for a subcommand (gateway client only, caused because of incorrectly unwrapping nested cmd data).
• Reduced total amount of spawned goroutines when handling interactions (gateway client only).
• Deleted PublicKey field from GatewayClientOptions (it was never used).

Full Changelog: amatsagu/tempest@v1.4.0...v1.4.1

v1.4.0

[!WARNING] With introduction of new client type, existing Discord Applications/Bots that rely on Tempest will be required to specify which client they want to use. Check example bot code for details on how to use either HTTPClient or GatewayClient. Bot code should be fully backward compatible.

What's Changed

• Added omitempty flag to TextInputComponent's label by @​SirzBenjie in amatsagu/tempest#46.
• Added basic tracing system (enable trace flag in settings of either client) - they are still far from ideal but should be helpful when dealing with weird library behavior.
• Removed support for HTTP event webhooks. This feature won't be supported anymore.
• Improved handler code for modal interactions.
• Added experimental, optional support of gateway session. Tempest is still library dealing exclusively with interactions. That being said, some highly active bots may find it beneficial to use gateway in order to have lower latency. Developers can set their own intents and handle any other, custom events on their own as needed. Current implementation should be backward compatible with existing Tempest Apps/Bots code.
• Split shared logic into BaseClient. HTTP & Gateway Clients use Base Client for shared functions. Base version remains public for potential modding needs.
• Added multiple gateway related structs to define activity, opcodes & events.

Full Changelog: amatsagu/tempest@v1.3.5...v1.4.0

v1.3.5

... (truncated)

Commits

• e26a3fe feat: prefer to use HTTP client in example app code
• 5378e8b feat: update example code to reflect shard manager changes
• 4700db6 feat: add once ready callback & improve methods to fetch shard status details
• 197ebc5 feat: update maintenance badge
• e3b95a6 fix: Use pointer method instead shallow cloning Guild struct
• d75a3fb fix: Use pointer to BaseClient instead calling old branch logic
• 8af9170 feat: Optimize hot paths in interactions by using direct pointers over branch...
• f06a9c2 feat: add for efficient data reading
• 3357e3e feat: add for efficient data reading
• 8706341 style: Update sub-command naming in example bot/app code
• 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 <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)