python310Packages.aiohttp: 3.8.1 -> 3.8.3

[dotlambda]

Description of changes

https://github.com/aio-libs/aiohttp/blob/v3.8.3/CHANGES.rst

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 22.11 Release Notes (or backporting 22.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
  • (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes
• Fits CONTRIBUTING.md.

[mweinelt]

I think this should be targeted at staging-next, given the number of rebuilds.

[dotlambda]

I think this should be targeted at staging-next, given the number of rebuilds.

Why staging-next, not staging?

[mweinelt]

The current staging-next is the last one before the branch-off.

[vcunat]

My reading of the schedule is that there's another one planned for 14th to 21st, but that one isn't supposed to bring any "breaking changes" (except perhaps in DEs).

[mweinelt]

Hm, indeed we can manage 7 days I think. And if we branch-off a day late that's fine with me.