[No767]

Summary

Waiting on wheels:

• valkey-glide (requires rust toolchain, protobuf compiler + zig compiler/build system. On their backlog for now)
• pyyaml (f5e4504a92f169f65350a1047dccb23bc97028be, waiting on wheels) Pyyaml maintainer has not bothered to publish the proper wheels. Using pyyaml-cp315 instead
• pycares (requires C compiler; builds just fine) Python 3.15 wheels released as of v5.2.0
• brotli (requires C compiler; builds just fine) Python 3.15 wheels released as of v1.2.1
• pyvips (requires C compiler; builds just fine) has to be extracted with pre-built binaries regardless of python version

Also when I refer to "C compiler", I'm referring to GCC

Types of changes

What types of changes does your code introduce to Kanae?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (Updates to README.md, the documentation, etc)
• Other (if none of the other choices apply)

Checklist

Put an x in the boxes that apply

• If code changes were made then they have been tested.
  • I have updated the documentation to reflect the changes. (if appropriate)
• All workflows pass with my new changes
• This PR does not address a duplicate issue or PR

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud