Release
A software release is a version of software made available for use or deployment, or the act of making that version available.
Elixir in Action, Third Edition
A release is a self-contained deployment artifact containing an application, its dependencies, compiled code, and the runtime needed to execute it.
- How it is used
- Packages an OTP system for standalone production deployment and supplies commands for starting, inspecting, and stopping it.
- How deep it goes
- Explains creation, environment selection, artifact contents, runtime independence, node configuration, and operational commands.
- Examples
- Uses a to-do release, Mix commands, generated shell commands, remote IEx sessions, and release load-path inspection.
- What you can do after
- Operate/configure a standalone release, select its build environment, run lifecycle commands, and attach to its production node.
Contract Testing in Action
A release is a software version designated as available or officially delivered, independently of whether it is currently deployed.
- How it is used
- Tracks versions made available in an environment, especially when multiple application versions remain in use.
- How deep it goes
- Distinguishes releases from deployments, demonstrates a broker command, and connects recording with environment-aware version selection.
- Examples
- Uses a MoviesAndroidApp production command, PactFlow integration records, and GraphQL deployment exercises.
- What you can do after
- Operate/configure Pact release recording with a participant, version identifier, and environment.
Grokking Software Architecture
A release is the product decision or action that makes software functionality available to its intended users.
- How it is used
- Separates the product decision to expose functionality from the engineering act of deploying code.
- How deep it goes
- Defines release against deployment and traces feature-flag control through dark launch to user activation.
- Examples
- Uses an enterprise-discount flag, internal QA access, and a dashboard switch to illustrate staged exposure.
- What you can do after
- Apply feature flags to deploy code without exposing it, then activate it for selected testers or users.
Think Like a CTO
A software release is a version of software made available for deployment or use, containing a defined set of changes or fixes.
- How it is used
- Makes software changes available while coordinating technical execution, business timing, stakeholder communication, and operational risk.
- How deep it goes
- Explains outage planning, documentation, communication, practice, and postmortems, but stops short of implementation-level tooling.
- Examples
- Uses outage releases involving downtime, data migration, maintenance pages, assigned runbook steps, progress reports, practice runs, and postmortems.
- What you can do after
- Operate/configure releases through documented steps, assigned responsibilities, stakeholder updates, contingency planning, and post-release learning.
Shipping Go: Develop, deliver, discuss, design, and go again
A release is a prepared software version made available for use by its intended recipients.
- How it is used
- Frames release as the delivery step that makes a product available for testing or use, distinct from operating it as a service.
- How deep it goes
- Explains binary publication, release timing, feedback, and version communication, but stops short of detailed release-versioning design.
- Examples
- Uses a pipeline.yml workflow, an api binary, a repository Releases page, and an externally reachable API tested by QA.
- What you can do after
- Apply it via GitHub Actions to publish a built binary as a tagged repository release for others to test or use.
Read how Shipping Go: Develop, deliver, discuss, design, and go again explains release →
Also covered in
- Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform
- The Art of Unit Testing 3e
- Bug BashIn early access (MEAP)
- GitHub Actions in Action: Continuous integration and delivery for DevOps
- Google Anthos in Action
- Building Web APIs with ASP.NET Core
- Build High Value Software SystemsIn early access (MEAP)
- Terraform in Depth: Infrastructure as Code with Terraform and OpenTofu
- BDD in Action, Second Edition
What to know first
- bugA software bug is a defect that can cause software to behave incorrectly or differently from its intended or specified behavior.
- productionProduction is the live operational setting in which a deployed software system serves its intended users or processes real workloads.
- continuous deploymentContinuous deployment is a software delivery practice in which changes that pass required validation are automatically released to a target environment, commonly production.
- environmentAn environment is the external context, system, or conditions within which an agent or application operates and interacts.
Related concepts
- deploymentcontrasts with · Deployment is the process of placing or releasing software, models, or configuration into a target environment so they can operate there.
- BEAMhas part · BEAM is the virtual machine and runtime environment that executes Erlang-family programs and applications.
- modulehas part · A module is a cohesive unit of code or computation that groups related functionality within a larger system and defines a scope or boundary for organizing or sharing it.
Questions about release
What is release?
A software release is a version of software made available for use or deployment, or the act of making that version available.
Which Manning books explain release?
Elixir in Action, Third Edition, Contract Testing in Action, Grokking Software Architecture, Think Like a CTO and Shipping Go: Develop, deliver, discuss, design, and go again.
What should I know before learning release?
Manning books that teach release usually introduce bug, production, continuous deployment and environment first.
What is the difference between release and deployment?
A software release is a version of software made available for use or deployment, or the act of making that version available. Deployment is the process of placing or releasing software, models, or configuration into a target environment so they can operate there.
What are the parts of release?
Release includes BEAM, module and release body.
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.




