Many complexities arose from 1.6.0 release (#503 breaking API), specially aiohttp breaking in production services, and fixing the yarl as aiohttp dependency and in production configuration becoming a big challenge.

To prevent something like this happening again, maybe yarl should have CI tests, at least as a warning, to ensure aiohttp passes tests with new changes, so big issues like that can be caught before a release is made?

If not a CI check, at least some scripts to be run manually.

What do you think?

Related convo:

• Patch update to older branches (2.0, 3.6, etc), to address yarl API-breaking minor update aiohttp#4987 (comment)