I'm recently started using Semantic Versioning.

But due to conflicts with my older versioning conventions (which I have written myself), I am very confused about the consideration of unit tests as a part of the Public API.

As mentioned by SemVer documentations:

Minor version Y (x.Y.z | x > 0) MUST be incremented if new, backward compatible functionality is introduced to the public API. It MUST be incremented if any public API functionality is marked as deprecated. It MAY be incremented if substantial new functionality or improvements are introduced within the private code. It MAY include patch level changes. Patch version MUST be reset to 0 when minor version is incremented.

I certainly believe that unit tests are a part of the public API as they can have huge effects on not only the quality of the source code, but even the functionality of the public API.

What should we do with our versioning system considering the importance and influence of the unit tests? How should they affect the versioning? Should they be considered in the versioning as a segment of the public API?

I recently started using Semantic Versioning.

Due to conflicts with my previous versioning convention (which I created myself), I am very confused about versioning unit tests as part of the public API.

As mentioned in the SemVer documentation:

Minor version Y (x.Y.z | x > 0) MUST be incremented if new, backward compatible functionality is introduced to the public API. It MUST be incremented if any public API functionality is marked as deprecated. It MAY be incremented if substantial new functionality or improvements are introduced within the private code. It MAY include patch level changes. Patch version MUST be reset to 0 when minor version is incremented.

I believe that unit tests are a part of the public API as they can have huge effects not only on the quality of the source code, but also on the functionality of the public API.

What should we do with our versioning system taking into account the importance and influence of unit tests? 

How should they affect versioning? 

Should they be considered in versioning as a segment of the public API?

Greetings

I'm a new developer who recently started using Semantic Versioning ( as it is the most humane method of software versioning ).

But dute to conflicts with my older versioning conventions ( which I have wrote myself and are purely unacceptable to the open-source community ), I am very confused about the consideration of unit tests as a part of the Public API.

as mentioned by SemVer documentations:

Minor version Y (x.Y.z | x > 0) MUST be incremented if new, backward compatible functionality is introduced to the public API. It MUST be incremented if any public API functionality is marked as deprecated. It MAY be incremented if substantial new functionality or improvements are introduced within the private code. It MAY include patch level changes. Patch version MUST be reset to 0 when minor version is incremented.

I ceartainly believe that unit tests ARE a part of the public API as they can have huge effects on not only the quality of the source code, but even the functionality of the public API.

what should we do with our versioning system considering the importance and influence of the unit tests? how should they effect the versioning? should they be considered in the versioning as a segment of the public API?

I'm recently started using Semantic Versioning.

But due to conflicts with my older versioning conventions (which I have written myself), I am very confused about the consideration of unit tests as a part of the Public API.

As mentioned by SemVer documentations:

Minor version Y (x.Y.z | x > 0) MUST be incremented if new, backward compatible functionality is introduced to the public API. It MUST be incremented if any public API functionality is marked as deprecated. It MAY be incremented if substantial new functionality or improvements are introduced within the private code. It MAY include patch level changes. Patch version MUST be reset to 0 when minor version is incremented.

I certainly believe that unit tests are a part of the public API as they can have huge effects on not only the quality of the source code, but even the functionality of the public API.

What should we do with our versioning system considering the importance and influence of the unit tests? How should they affect the versioning? Should they be considered in the versioning as a segment of the public API?

Greetings

I'm a new developer who recently started using Semantic Versioning ( as it is the most humane method of software versioning ).

But dute to conflicts with my older versioning conventions ( which I have wrote myself and are purely unacceptable to the open-source community ), I am very confused about the consideration of unit tests as a part of the Public API.

as mentioned by SemVer documentations:

Minor version Y (x.Y.z | x > 0) MUST be incremented if new, backward compatible functionality is introduced to the public API. It MUST be incremented if any public API functionality is marked as deprecated. It MAY be incremented if substantial new functionality or improvements are introduced within the private code. It MAY include patch level changes. Patch version MUST be reset to 0 when minor version is incremented.

I ceartainly believe that unit tests ARE a part of the public API as they can have huge effects on not only the quality of the source code, but even the functionality

After all, what should we do with our versioning system considering the importance and influence of the unit tests? how should they effect the versioning? should they be considered in the versioning as part new features?

Greetings

I'm a new developer who recently started using Semantic Versioning ( as it is the most humane method of software versioning ).

But dute to conflicts with my older versioning conventions ( which I have wrote myself and are purely unacceptable to the open-source community ), I am very confused about the consideration of unit tests as a part of the Public API.

as mentioned by SemVer documentations:

Minor version Y (x.Y.z | x > 0) MUST be incremented if new, backward compatible functionality is introduced to the public API. It MUST be incremented if any public API functionality is marked as deprecated. It MAY be incremented if substantial new functionality or improvements are introduced within the private code. It MAY include patch level changes. Patch version MUST be reset to 0 when minor version is incremented.

I ceartainly believe that unit tests ARE a part of the public API as they can have huge effects on not only the quality of the source code, but even the functionality of the public API.

what should we do with our versioning system considering the importance and influence of the unit tests? how should they effect the versioning? should they be considered in the versioning as a segment of the public API?