CODEWITHSUNDEEP
csssemantic-versioning
Mike Hamilton
Mike Hamilton

Reputation: 1567

How to semantically version a change to a CSS color property

I maintain a CSS framework and am trying to follow semantic versioning in a way that makes the most sense. Would changing the value of non critical property (like the color of an element) be considered a minor change or a patch change? If I am at version 0.5.0 but want to release an update with no new features just changes to some colors, should I release as 0.5.1 or 0.6.0?

While a color change won't exactly "break" a code base, I could see how to some this should be considered a minor change. But for the sole fact that this kind of change is not adding a feature is why I could also see it being just a patch change. Hoping to learn if there is an generally accepted standard for this situation.

Upvotes: 0

Views: 403

Answers (1)

taringamberini
taringamberini

Reputation: 2747

Actually Bootstrap adopts Semantic Versioning 2.0.0 even if I wasn't able to find how they have defined the API.

I have seen an attempt to define a CSS API and another one but I'm not totally satisfied.

About colors I have always wondered about including in the API the version of a validation tool for accessibility and setting some thresholds. The thresholds are mapped to minor or patch. But it's only a raw idea.

Upvotes: 0

Related Questions