A new plugin URL matching API was introduced in 2.3.0 which will help Streamlink with static code analysis and an improved
plugin loading mechanism in the future. Plugins now define their matching URLs and priorities declaratively.
The old can_handle_url and priority classmethods have therefore been deprecated and will be removed in the future.
When side-loading plugins which don't implement the new @pluginmatcher but implement the old classmethods, a deprecation
message will be written to the info log output for the first plugin that gets resolved this way.
Plugins which have more sophisticated logic in their can_handle_url() classmethod need to be rewritten with
multiple @pluginmatcher decorators and/or an improved _get_streams() method which returns None or raises a
NoStreamsError when there are no streams to be found on that particular URL.
Streamlink's default config file paths got updated and corrected on Linux/BSD, macOS and Windows.
Old and deprecated paths will be dropped in the future.
Only the first existing config file will be loaded. If a config file gets loaded from a deprecated path,
a deprecation message will be written to the info log output.
To resolve this, move the config file(s) to the correct location or copy the contents of the old file(s) to the new one(s).
Please note that this also affects all plugin config files, as they use the same path as the primary config file but with
.pluginname appended to the file name, eg. config.twitch.
On Windows, when installing Streamlink via the Windows installer, a default config file gets created automatically due
to technical reasons (bundled ffmpeg and rtmpdump dependencies). This means that the Windows installer will create a
config file with the new name when upgrading from an earlier version to Streamlink 2.2.0+, and the old config file won't be
loaded as a result of this.
This is unfortunately a soft breaking change, as the Windows installer is not supposed to touch user config data and the
users are required to update this by themselves.