Bump jishaku from 1.20.0.220 to 2.5.0

[dependabot]

Bumps jishaku from 1.20.0.220 to 2.5.0.

Release notes

Sourced from jishaku's releases.

jishaku 2.5.0

https://pypi.org/project/jishaku/2.5.0/ https://github.com/Gorialis/jishaku/tree/2.5.0 https://jishaku.readthedocs.io/en/latest/whatsnew.html#version-2-5-0

It is advised that you install jishaku directly through the pip package manager.

Install the latest version of jishaku:

pip install -U jishaku

Install specifically this version of jishaku (not recommended):

pip install -U jishaku==2.5.0

Artifacts are included with this release for debugging convenience.

jishaku 2.4.0

https://pypi.org/project/jishaku/2.4.0/ https://github.com/Gorialis/jishaku/tree/2.4.0 https://jishaku.readthedocs.io/en/latest/whatsnew.html#version-2-4-0

It is advised that you install jishaku directly through the pip package manager.

Install the latest version of jishaku:

pip install -U jishaku

Install specifically this version of jishaku (not recommended):

pip install -U jishaku==2.4.0

Artifacts are included with this release for debugging convenience.

jishaku 2.3.2

https://pypi.org/project/jishaku/2.3.2/ https://github.com/Gorialis/jishaku/tree/2.3.2 https://jishaku.readthedocs.io/en/latest/whatsnew.html#version-2-3-2

It is advised that you install jishaku directly through the pip package manager.

Install the latest version of jishaku:

pip install -U jishaku

... (truncated)

Changelog

Sourced from jishaku's changelog.

Version 2.5.0

This version adds mostly-complete strict typing to the library, supporting type checkers using the public API.

jsk sync has also been improved, now including a diagnostic for commands that fail to sync, and the ability to use $ to sync global commands, . to sync the current guild, and * to sync all known guilds.

Version 2.4.0

discord.py has now resumed development, and this version allows the cog to be loaded with the new 2.0a async load strategy.

As it stands, jishaku will now once again handle discord.py as its first class priority for support. However, jishaku will still no longer serve discord.py as a requirement and fork-specific fixes up to this point will remain, with future ones still being considered based on their impact.

It is still thus up to you what you decide to use with jishaku, and the module will not make this choice for you, but be aware that discord.py-related bugs will be prioritized for fixes over other implementations.

New stuff in this release:

• jishaku will now correctly provide and use async setup/add_cog/load_extension on 2.0a
• __main__ has been improved to allow you to specify a log file to output to in addition to stdout.
• WrappedPaginator performance has been improved over tenfold, reducing lag from extremely large outputs
• The jsk sync command has been added, allowing you to sync either your global or guild-specific app_commands.
• jsk pyi now by default includes the help text on objects when it can find it, making it quicker to determine how to use functions and classes.
• The jsk ast command has been added, which takes in code and produces a colourful AST breakdown tree.
• The jsk command will now correctly detect and display the version of the source of the discord package on forks.
• The jsk command will now show whether the message_content intent is enabled or not.
• The jsk sh support will now attempt to preserve and properly display ANSI when it is possible to do so.
• The jsk sh command has a new alias: jsk terminal.
• The jsk vc ytdl command will now prioritize yt-dlp when it's available to take advantage of the reduced staggering.
• The ALWAYS_DM_TRACEBACK flag has been added to always DM tracebacks, even for syntax errors.
• The USE_ANSI_ALWAYS and USE_ANSI_NEVER flags have been added to override ANSI use in commands that support it.
• Typing has been improved across the module.

Version 2.3.2

Fixed a regression from 2.3.1 that made permtrace return bad results on 1.7.2

Version 2.3.1

This is a patch release to fix a number of issues with permtrace and improve __main__.

Version 2.3.0

... (truncated)

Commits

• See full diff 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]

Superseded by #277.