Change "outdated" color semantic

[mbrodala]

The outdated command currently outputs updates in red; if the update is breaking according to semver it is displayed in yellow.

Since red matches the "error" state and yellow the "warning" state, one would expect the less breaking change to be yellow and the definitely breaking change to be red. Thus I think these two colors should be swapped.

What do you think?

[alcohol]

I think that would better match expectations indeed.

[Seldaek]

The colors have been picked to match colors used by npm outdated, and they are documented. The point is that updates marked red are more important/urgent as they are easy to do. While the semver-breaking changes in yellow are less relevant as they might require you to update the app.

[mbrodala]

OK, so the color reflects the relevance, not necessarily the severity. Gotta keep this in mind unless you change yours. ;-)

[Seldaek]

I rather keep "mind compatibility" with npm when possible :)

[c33s]

basically i understand the decision to match npm but sticking with something semantically wrong only because other system stick to a wrong semantic is maybe not the best choice.

sidenote:
thank you for this awesome project. composer is really a rocksolid application. thank you for all your work.

[ThomasLandauer]

I just suggested to add a "legend" below the output to clarify the meaning of the colors: #9716