[14:40:39] <anomie>	 Would someone mind tagging a release for mediawiki-codesniffer? I'm wanting to import some of its rules in a third-party project, and I'd rather not depend on dev-master to get a dependency on squizlabs/php_codesniffer 3.5.6+.
[14:41:26] <anomie>	 For that matter, it'd be nice if it'd have a looser dependency and let MediaWiki itself declare something more strict if it wants.
[14:52:18] <Reedy>	 I'm guessing it's purposely done strict to stop it automatically updating itself in patches and then unrelated phpcs failures coming...
[14:54:53] <Reedy>	 Jees. It's a while since the last release was tagged
[14:56:58] * Reedy filed https://phabricator.wikimedia.org/T266476
[15:17:32] <legoktm>	 anomie: o/ we had to pin upstream PHPCS because they didn't have any stability guarantee that stuff wouldn't start failing in patch releases
[15:38:00] <anomie>	 It does make it difficult to keep things in sync if you're taking packages from multiple sources though. Most other "standards" repos seem to declare a dependency with ^, and then presumably declare a strict dependency in the actual code repos.
[15:45:06] <legoktm>	 that seems reasonable, I think we just haven't had enough external users (yet!) to make that worthwhile
[15:52:44] <anomie>	 legoktm: Well, if it helps, https://github.com/Automattic/jetpack/pull/17406
[15:54:53] <legoktm>	 ooh
[15:54:58] <legoktm>	 I'll have the new release out in a few minutes