How deeply does Go in Action, Second Edition cover semantic versioning?

Defines major, minor, and patch changes, then shows release tagging; does not elaborate on version-selection rules.

Semantic versioning

As explained in Go in Action, Second Edition

Semantic versioning is a versioning convention in which changes to major, minor, and patch components communicate compatibility and release significance.

A published Go module needs a version so other modules can identify a release and judge whether an update is compatible. Semantic versioning uses the form vMAJOR.MINOR.PATCH: increment MAJOR for incompatible API changes, MINOR for backward-compatible functionality, and PATCH for backward-compatible bug fixes. section 11.2

For an initial domain-module release, commit the entities and interfaces, then tag the commit domain/v0.0.1. In a repository with multiple modules, the domain/ prefix tells Go which module the tag belongs to. A storage module can then depend on that version while implementing the domain.Storage interface. section 11.2

cd domain
git add .
git commit -m "Initial domain module with core entities and interfaces"
git tag domain/v0.0.1
git push origin domain/v0.0.1

Commands to commit, tag, and push the initial domain-module release. section 11.2

How Go in Action, Second Edition covers it

liveBook manning.com

Read Go in Action, Second Edition on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Building Web APIs with ASP.NET CoreSemantic versioning is a version-numbering convention using MAJOR, MINOR, and PATCH components whose increments communicate compatibility and change significance.
liveBook manning.com

API Design PatternsA semantic version string is a dotted three-number representation whose major, minor, and patch components communicate the nature of software changes.
liveBook manning.com

The Design of Web APIs, Second EditionA semantic version number is a version identifier with major, minor, and patch components whose changes conventionally communicate compatibility impact.
liveBook manning.com

The Art of CodeSemantic versioning is a version-numbering convention in which major, minor, and patch components communicate compatibility and change significance.
liveBook manning.com

GitHub Actions in Action: Continuous integration and delivery for DevOpsSemantic versioning is a versioning scheme that communicates compatibility and change significance through major, minor, and patch version numbers.
liveBook manning.com

Infrastructure as Code, Patterns and Practices: With examples in Python and TerraformSemantic versioning is a version-numbering scheme in which major, minor, and patch components communicate the kinds of changes between releases.
liveBook manning.com

Terraform in Depth: Infrastructure as Code with Terraform and OpenTofuA semantic version is a version identifier following major, minor, and patch precedence rules.

Compare how 8 books explain semantic versioning →

Related concepts

major versionhas part · A major version is the primary component of a version identifier that distinguishes a release line and commonly signals potentially backward-incompatible changes.
FluentBitused by · Fluent Bit is a lightweight, open-source telemetry agent for collecting, processing, enriching, and forwarding logs and other event data.

This explainer was generated by Manning's knowledge graph from the text of Go in Action, Second Edition. The section links point to the parts of the book it draws on.