title: Does the introduction of authentication justify a major-version bump according to Semantic-Versioning?
body: <p>semver.org states:</p>
  <blockquote>
  <p>Given a version number MAJOR.MINOR.PATCH,</p>
  <p>increment the [..] MAJOR version when you make incompatible API changes</p>
  </blockquote>
  <p>I have a Maven-Plugin, that gathers some data and sends it (via REST) to a server component.
  Unsecured until now.</p>
  <p>So, if I don't change the API iself, but introduce changes, that would render an older version of the Maven-Plugin useless without the newly added process and configuration, shouldn't I increment the MAJOR version?</p>