Audience asked how Blimke follows changes in the HTTP-client libraries WebMock cooperates with. Answer: WebMock's Gemfile does not hardcode versions or version restrictions, so CI always runs against the latest version of each gem — meaning some old versions may stop working. There is no automated system for tracking incompatibilities; Blimke usually finds out when tests start failing on rerun or when users open issues. Often an issue is first opened against the HTTP-client gem and its maintainer or a contributor submits a PR to WebMock, or someone raises a parallel issue on WebMock directly. These issues are usually served first because they affect a large number of users.