Bump twilight-model from 0.2.6 to 0.3.0

[dependabot-preview]

Bumps twilight-model from 0.2.6 to 0.3.0.

Release notes

Sourced from twilight-model's releases.

cache-inmemory: 0.3.0

Upgrade Path

Instead of specifying individual events to process via config::EventType, specify individual resources to process. For example, previously enabling the EventType::MESSAGE_CREATE and EventType::MESSAGE_DELETE event types were intended to cache the messages, members, and users within these message events. Now ResourceType::MESSAGE can be specified to cache the messages from all message events, but not the users and members. This avoids an inconsistent cache and not enabling all of a grouping of an event type was typically an error.

Changes

Replace config::EventType with a simpler and less error prone config::ResourceType (#660 - @vivian).

#660: twilight-rs/twilight#660

command-parser: 0.3.0

This major version bump of the Embed Builder crate is done to match all of the other crates in the ecosystem receiving a major version bump. There are no changes.

embed-builder: 0.3.0

This major version bump of the Embed Builder is done to match all of the other crates in the ecosystem receiving a major version bump. There are no changes.

gateway-queue: 0.3.0

This major version bump of the Gateway Queue is done to match all of the other crates in the ecosystem receiving a major version bump. There are no changes.

gateway: 0.3.0

Version 0.3 has been released with the primary intent to upgrade to Tokio 1.0.

Upgrade Path

When using shard::Sink pass in the new shard::raw_message::Message type instead of tungstenite::Message. This is mostly equivalent to tungstenite's message but prevents exposing it directly, which avoids API breakage when upgrading internal websocket dependencies.

Changes

Hide the tungstenite dependency from the public API by creating an equivalent to a websocket message that can be constructed and passed in (#667 - @vivian).

Upgrade tokio from v0.2 to v1 (#664 - @vivian).

#667: twilight-rs/twilight#667 #664: twilight-rs/twilight#664

http: 0.3.0

Version 0.3 has been released with the primary intent to switch from reqwest to the lighter hyper as the HTTP client and upgrade to Tokio 1.0.

Upgrade Path

client::Client's delete_webhook_from_url, execute_webhook_from_url, update_webhook_from_url, and update_webhook_with_token_from_url methods have been removed. Instead, use the twilight-util crate's new link::webhook::parse functionality to parse webhook IDs and tokens out of URLs. Then, pass the webhook ID and token to the method variants without _from_url; for example, client::Client::execute_webhook.

client::Client::add_role has been removed because it was a duplicate method. Instead use client::Client::add_guild_member_role.

When attaching files to a message, pass in the bytes of the attachment instead of reqwest's Body type.

If supplying an HTTP client to twilight-http, pass a hyper client instead of a reqwest client and use client::ClientBuilder::hyper_client instead of reqwest_client.

Commits

• b80a77d release(http): bump to v0.3.0
• 290c50c release(lavalink): bump to v0.3.0
• 7d0247d release(mention): bump to v0.3.0
• 0b56949 release(model): bump to v0.3.0
• a27af4e release(standby): bump to v0.3.0
• a726b3d release(util): bump to v0.3.0
• 9fe4350 chore!(http): remove re-exports (#673)
• 79d6caf feat!(model): use vecs instead of hashmaps (#659)
• 343ecac chore(http,lavalink): remove hyper's http1 feature (#670)
• 8ef3211 refactor!(cache/in-memory): resource types over event types
• 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 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)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[dependabot-preview]

Superseded by #29.