Bump hikari from 2.0.0 to 2.2.0

[dependabot]

Bumps hikari from 2.0.0 to 2.2.0.

Release notes

Sourced from hikari's releases.

2.2.0 (2025-03-21)

Breaking Changes

• Remove PartialInteraction.get_channel and PartialInteraction.fetch_channel. You can directly use PartialInteraction.channel instead (#1621)

• User commands breaking changes:

  • Remove previously deprecated command_interactions.InteractionChannel and command_interactions.ResolvedOptionData
  • CommandInteraction.app_permissions is no longer optional
  • Removal of Commands.dm_permissions and Message.interaction. Use Commands.contexts and Message.interaction_metadata respectively (#2195)

• Remove with_expiration parameter from REST client's fetch_invite method.

  • The parameter has been a noop for a while as Discord removed it (#2224)

Features

• Several new PartialInteraction features:

  • Add new PartialInteraction.channel attribute
  • Moved common interaction fields to PartialInteraction
  • app_permissions is now available for all interaction types
  • Add missing fields to InteractionChannel (#1621)

• Add missing fields to AuditLogEventType (#1991)

• Add user installations support (#2177)

2.1.1 (2025-02-26)

Features

• Allow specifying a reason for message deletions (#2066)
• Allow setting name and value of an EmbedField to an empty string. (#2105)

Bugfixes

• Fixed Entitlement starts_at and ends_at erroring when set to None. (#2149)
• Properly handle and error on Cloudflare bans (#2168)

Documentation Improvements

• Added missing documentation for GatewayShard and for trait ShardAware, adding missing errors which can be thrown. (#2100)

2.1.0 (2024-09-25)

Breaking Changes

• VoiceState.member can now be None in cases where Discord doesn't send the relevant information (#2038)

Features

• Add the optional audit log reason argument to hikari.api.rest.RESTClient.delete_channel and hikari.impl.rest.RESTClientImpl.delete_channel, the same way it already exists for e.g. edit_channel (#2058)

... (truncated)

Changelog

Sourced from hikari's changelog.

2.2.0 (2025-03-21)

Breaking Changes

• Remove PartialInteraction.get_channel and PartialInteraction.fetch_channel. You can directly use PartialInteraction.channel instead (#1621)
• User commands breaking changes:
  • Remove previously deprecated command_interactions.InteractionChannel and command_interactions.ResolvedOptionData
  • CommandInteraction.app_permissions is no longer optional
  • Removal of Commands.dm_permissions and Message.interaction. Use Commands.contexts and Message.interaction_metadata respectively (#2195)
• Remove with_expiration parameter from REST client's fetch_invite method.
  • The parameter has been a noop for a while as Discord removed it (#2224)

Features

• Several new PartialInteraction features:
  • Add new PartialInteraction.channel attribute
  • Moved common interaction fields to PartialInteraction
  • app_permissions is now available for all interaction types
  • Add missing fields to InteractionChannel (#1621)
• Add missing fields to AuditLogEventType (#1991)
• Add user installations support (#2177)

---

2.1.1 (2025-02-26)

Features

• Allow specifying a reason for message deletions (#2066)
• Allow setting name and value of an EmbedField to an empty string. (#2105)

Bugfixes

• Fixed Entitlement starts_at and ends_at erroring when set to None. (#2149)
• Properly handle and error on Cloudflare bans (#2168)

Documentation Improvements

• Added missing documentation for GatewayShard and for trait ShardAware, adding missing errors which can be thrown. (#2100)

---

2.1.0 (2024-09-25)

Breaking Changes

• VoiceState.member can now be None in cases where Discord doesn't send the relevant information (#2038)

Features

• Add the optional audit log reason argument to hikari.api.rest.RESTClient.delete_channel and hikari.impl.rest.RESTClientImpl.delete_channel, the same way it already exists for e.g.

... (truncated)

Commits

• 2c415b8 Run uv sync before checking hikari output
• 52770ed Prepare for release of 2.2.0 (#2249)
• 3ceb3fc Use correct token for pre release workflow (#2248)
• 10ee685 Fix prerelease flow (take 2) (#2247)
• 7f3bf35 Fix prepare release workflow (#2246)
• d913caa Update astral-sh/setup-uv action to v5.4.0 (#2245)
• e11dcfe Add new interaction channel attribute (#1621)
• 6fe92e7 Update dependency ruff to v0.11.2 (#2243)
• 54a4637 Remove outdated rillrate example (#2242)
• 16465f4 Use uv as package manager in the contribution guide (#2228)
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[dependabot]

A newer version of hikari exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.