liveBook · Manning

Version

A version is a distinct, identifiable state or revision of an artifact, system, or product.

How 7 Manning books explain it

The Design of Web APIs, Second Edition

An API version is a distinct, identifiable state of an API contract that may differ from other versions in its supported behavior or representation.

How it is used
Identifies an API contract so consumers can choose a supported state and migrate when changes would break their applications.
How deep it goes
Works through request representation, parallel-version trade-offs, and OpenAPI notation, while leaving detailed breaking-change procedures to separate treatment.
Examples
Uses a breaking product-price change, /v2/accounts, a Version header, and an OpenAPI info.version value.
What you can do after
Apply it via an API versioning policy: choose an identifier and request form, assess migration costs, and document the contract version.

Read how The Design of Web APIs, Second Edition explains version →

Go in Action, Second Edition

A version number is an identifier representing a particular software release or state, often communicating its compatibility or maturity.

How it is used
Uses versions to communicate compatibility and coordinate independent releases across Go modules.
How deep it goes
Explains semantic version components, module-prefixed tags, dependency selection, and independent release histories.
Examples
Uses domain, storage, API, and worker modules to demonstrate tagged releases and versioned dependencies.
What you can do after
Apply it via Git and Go tooling to tag module releases and select dependency versions.

Read how Go in Action, Second Edition explains version →

Kubernetes in Action, Second Edition

An API version identifies a versioned Kubernetes API schema for a resource kind, including its available fields and default values.

How it is used
Identifies the schema Kubernetes uses to read, validate, expose, and describe a resource kind.
How deep it goes
Explains schema differences, default values, API groups, resource representations, and kubectl inspection, but not version conversion internals.
Examples
Uses v1 Node and Pod manifests, apps/v1 Deployments, and historical extensions/v1beta1 Deployment access.
What you can do after
Apply it via kubectl by selecting compatible apiVersion values and inspecting schemas with kubectl explain.

Read how Kubernetes in Action, Second Edition explains version →

AI Model Evaluation

A model version is a distinct released or identified state of a model with a specific implementation, parameters, or training artifacts.

How it is used
Uses versions to trace evaluation results, detect silent evaluator changes, and diagnose whether score movement reflects a genuine regression.
How deep it goes
Operationalizes versioning through identifiers, hashes, canaries, logs, and triage, without descending into model implementation internals.
Examples
Uses dated evaluator identifiers, output hashes, fixed canary prompts, and a search event containing the ranking policy version.
What you can do after
Diagnose evaluation changes by separating data, judge, prompt, instability, and evaluated-model causes.

Read how AI Model Evaluation explains version →

Amazon Web Services in Action, Third Edition: An in-depth guide to AWS

An object version is a distinct stored revision of an object identified by the same object key.

How it is used
Supports S3 backup and archiving by retaining earlier object revisions.
How deep it goes
Defines overwrite behavior, demonstrates preservation and retrieval, and notes storage-cost growth without covering lifecycle management.
Examples
Uses repeated uploads of data 1 and data 2 under object key A, followed by listing and downloading versions.
What you can do after
Apply versioning via AWS CLI, list revisions, and restore earlier object data.

Read how Amazon Web Services in Action, Third Edition: An in-depth guide to AWS explains version →

Learn PowerShell Scripting in a Month of Lunches, Second Edition: Write and organize scripts and tools

A script version is a release identifier recorded in a script's metadata to distinguish one published revision from another.

How it is used
Tracks published module and script revisions during PowerShell packaging, distribution, and maintenance.
How deep it goes
Explains where to record versions, when to increment them, and how to hide prior releases, without detailing a complete release policy.
Examples
Uses 1.0.0, manifest ModuleVersion, script file-info headers, republishing, and hiding versions from gallery search results.
What you can do after
Operate publishing workflows by updating metadata, republishing revisions, retrieving releases, and hiding obsolete versions.

Read how Learn PowerShell Scripting in a Month of Lunches, Second Edition: Write and organize scripts and tools explains version →

Effective Platform Engineering

An API version is an identifier that distinguishes a particular compatibility and behavior contract for an API.

How it is used
Manages Kubernetes API compatibility across promotions, upgrades, deprecations, and removals.
How deep it goes
Explains deprecation timing, compatibility windows, cluster scanning, and team notification, but not versioning implementation internals.
Examples
Uses admission registration and deployment manifests, plus an upgrade watcher that creates Jira issues for affected teams.
What you can do after
Diagnose outdated API usage and coordinate migrations before a Kubernetes release removes compatibility.

Read how Effective Platform Engineering explains version →

Also covered in

What to know first

Related concepts

Questions about version

What is version?

A version is a distinct, identifiable state or revision of an artifact, system, or product.

Which Manning books explain version?

The Design of Web APIs, Second Edition, Go in Action, Second Edition, Kubernetes in Action, Second Edition, AI Model Evaluation, Amazon Web Services in Action, Third Edition: An in-depth guide to AWS, Learn PowerShell Scripting in a Month of Lunches, Second Edition: Write and organize scripts and tools and Effective Platform Engineering.

What should I know before learning version?

Manning books that teach version usually introduce JSON, contract, language model and deployment first.

What is the difference between version and control group?

A version is a distinct, identifiable state or revision of an artifact, system, or product. A control group is a set of experimental units assigned to a baseline or comparison condition for evaluating an intervention or alternative.

What is version part of?

Version is part of manifest file. A manifest file is a machine-readable document that declares metadata, configuration, contents, or resources associated with a software artifact, application, or collection.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.