real client = the client package that we executed the release’s test. -> means nested providers from the real client. For example p->[email protected] means that p2 is the p’s provider and p is the real client’s provider. --------------------------------------------------------------------- 1) [email protected] changed a key in its code, that did not introduce an error, but it became incompatible with babel-eslint. The escope is not a babel-eslint’s provider. This error was fixed by [email protected], when its providers claimed that it should be fixed in babel-eslint. ● Issue in babel-eslint ● Issue in escope ● Pull-request in babel-eslint ● Fixed by provider babel-eslint, which is the provider of the real client. ● Category: incompatible providers version. 2) the real client has grunt-jslint->jslint@>=0.3.4 as its providers. The [email protected] started to use ES6 and moved all of ES5’s code to another file. The [email protected] did a downgrade in the jslint’s version. Specifically, the grunt-jslint uses the array JSLINT.error, which was moved to another file. jslint is a provider of grunt-jslint, and grunt-jslint is a provider of real client. ● Downgrade of jslint ● [email protected] diff ● [email protected] changelog ● Fixed by provider as client grunt-jslint, which is the client of jslint. ● Category: Feature change. 3) the real client has the [email protected] as its provider. The babel-preset-es2015-rollup has the babel-preset-es2015 as its provider, that is introducing an error. The [email protected] introduced a new format that became an error in babel-preset-es2015-rollup, which had to fix this error in its version 1.2.0. ● [email protected] change. ● babel-preset-es2015-rollup issue (fix). ● Fixed by provider as client babel-preset-es2015-rollup, which is client of babel-preset-es2015. ● Category: Feature change. 4) [email protected] is not compatible with prop-types@>15. The real client uses the [email protected]. The real client also uses provider [email protected] -> rc- [email protected] -> prop-types@15. The [email protected] fixes this incompatibility. ● Prop-types compatibility. ● [email protected] fixes this incompatibility. ● Fixed by provider react, which is the provider of the real client. ● Category: incompatible providers version. 5) The real client has a provider [email protected] that wrote a wrong code: const pattern = pattern = '^(' // same var twice The clients did a downgrade and, then, an upgrade. ● pull-request. ● Client downgrade and upgrade. ● Fixed by (first) client and by provider front-matter. ● Category: Wrong code. 6) The real client has a provider grunt-testacular@*. The grunt- [email protected] changed the task name from “testacularServer” to “testacular”. Neither provider or client fixed this error. ● [email protected] change. ● Category: Feature change. 7) The real client has a provider nosql-memdb@>=0.11.3. In release 0.11.4, nosql-memdb returned an object to callback. In release 0.11.5, this object was removed from callback, fixing the error. The real client updated to nosql- memdb@>=0.11.5. ● abstract-iterator error and fix. ● real client update the abstract-iterator version. ● Fixed by provider abstract-iterator. ● Category: Object type change (undefined was returned, then a new NotFoundError(), then undefined again). 8) The real client uses eslint@0.* as its provider. The [email protected] changed the rule no-comma-dangle to comma-dangle and marked it as a breaking in changelog. The real client removed the eslint provider and replaced it with standart. ● [email protected] changelog. ● The real client replaced the eslint by standart. ● Fixed by client. ● Category: Feature change. 9) The eslint-config-airbnb -> eslint-config-airbnb-base@^11.0.1 is the client’s provider. The [email protected] changed the rule no-param-reassign introducing a new property. This property just works with eslint@^3.18.0. The real client updated its providers to fix this error. ● eslint-config-airbnb-base change. ● eslint-config-airbnb-base and eslint compatibility. ● real client fix. ● Fixed by provider [email protected] and then by the real client. ● Category: Incompatible provider versions. 10) the real client uses the imagemin->imagemin-optipng@^4.0.0. The [email protected] changed the values in one array and broke the client. This error was fixed by the client. ● [email protected] change. ● real client fix. ● Fixed by client. ● Category: Feature change. 11) The real client uses the react-redux-provide->react-redux@^4.0.0. The [email protected] removes its implementation of a function isPlainObject and starts to use isPlainObject directly from lodash. So, the client [email protected] fixes this error replacing the provider. ● [email protected] change. ● [email protected] replacing the provider to is-plain- object@^2.0.1. ● Fixed by provider as client react-redux-provide. ● Category: Object type changed (isPlainObject changed from the react- redux’s implementation to the lodash’s implementation). 12) The real client uses the enzyme@^2.7.1 as its provider. The [email protected] starts to support [email protected], but it requires another dependency: react-test- renderer. Neither the real client or its providers have react-test-renderer as dependency. So, the client breaks. Then, [email protected] fixes its code. Then, the real client adds react-test-renderer as its provider. ● [email protected] change. ● [email protected] fix. ● The real client fix. ● Fixed by provider [email protected] and after by client. ● Category: Feature change (it may be similar to an incompatible provider change, but I believe the [email protected] change did not become incompatible with no one). 13) The real client has test-machinepack-mocha -> test- machinepack@^2.1.0 as its providers. The [email protected] removes one of its providers and tries to implement its own code, to replace the provider. He implements your own runInstantiatedMachine object. The test- machinepack-mocha updated the test-machinepack to fix its code. ● test-machinepack change. ● test-machinepack-mocha update. ● Fixed by provider as client test-machinepack-mocha. ● Category: Object type changed (The object runInstantiatedMachine was changed to its own implementation). 14) The real client has the esprima-extract-comments->esprima@git (actually, this esprima is a fork for the original one) as its providers. The esprima added its main file, the dist/esprima.js, to .gitignore. So, exprima-extract- comments cannot import esprima directly from git. The esprima-extract- comments fixed it depending on esprima directly from npm. ● esprima removes and adds its file to .gitignore. ● esprima-extract-comments fixes. ● Fixed by provider as client exprima-extract-comments. ● Category: File not Found. 15) The real client has the fakeredis->redis@^2.4.0 as its dependencies. The [email protected] changes the name of one function and breaks fakeredis. So, fakeredis does a downgrade to [email protected] and fixes the error. ● redis renames function. ● fakeredis fixes redis. ● Fixed by provider as client fakeredis. ● Category: Renamed Function. 16) The real client has jsdom@~0.10.5 as its provider. jsdom was created without a set method. So, when the Array.prototype.splice tried to set the length property, it broke. It was fixed by [email protected], when a set method was created. The client did not fix anything. ● jsdom fixes. ● Fixed by provider. ● Category: undefined object. 17) The real client has @types/lodash-es->@types/lodash@* as its provider. The @types/[email protected] changed the type of an object and broke the client’s build. Neither provider or client fixed this error. ● @types/lodash change. ● Category: Object type change. 18) The real client has karma-remap-istanbul -> remap-istanbul -> source- map@>=0.5.0. The [email protected] returns new Promise() instead of a previous object. The remap-istanbul did a downgrade in source-map. ● source-map change. ● remap-istanbul fix. ● Fixed by provider as client remap-istanbul. ● Category: Object type change. 19) The real client has ember-cli -> broccoli-merge-trees -> broccoli- plugin@^1.3.0 and ember-cli-qunit@^1.4.0 as its providers. The ember- [email protected] changed the type of an object that was returned and it worked well. Then, [email protected] changed the way of validation the objects, and the object changed in [email protected] was not recognized. Thus, [email protected] fixed the object type to be recognized. ● [email protected] change. ● [email protected] change. ● [email protected] fix. ● Fixed by provider ember-cli-qunit. ● Category: incompatible provider versions. 20) The real client has docpad->cson->js2coffee@~0.2.3 as its provider. The [email protected] changed the preinstall script to execute with npm run-script instead of node. In [email protected] it was fixed reverting the preinstall script to node. Then, cson updated to js2coffee@~0.3.1. ● [email protected] change. ● [email protected] fix. ● cson update. ● Fixed by provider and by client (cson) after. ● Category: Wrong code. 21) The real client updated its mongodb provider from 1.2.x to 1.3.x. The [email protected] changed the way an error should be emitted. So, the real client updates its code and mongodb’s version to adapt itself with the change.