What is a good versioning strategy for deployment artifacts?

What is a good versioning strategy for deployment artifacts?

• A. Version everything with incremental numbers only.
• B. Use dates as versions.
• C. Semantic versioning with immutable image tags and builds tied to commits for traceability.
• D. Version is not necessary for deployments.

Answer: (C)

A robust versioning strategy for deployment artifacts should provide clear meaning about changes, reproducibility, and traceability. Semantic versioning gives you explicit signals about the nature of a change—major updates may break compatibility, minor updates add functionality while staying backward-compatible, and patches fix bugs without changing behavior. When you combine semantic versioning with immutable image tags, you ensure that once a version is published, it cannot be altered, so environments that depend on that tag will always get the same artifact. Linking each build to a specific commit further strengthens traceability, letting you identify the exact source state that produced a given artifact and enabling precise audits or rollbacks. This approach beats other strategies because incremental numbers alone provide little context about impact, date-based versions can be ambiguous about compatibility and upgrade paths, and not versioning at all destroys the ability to reproduce or roll back deployments.

A robust versioning strategy for deployment artifacts should provide clear meaning about changes, reproducibility, and traceability. Semantic versioning gives you explicit signals about the nature of a change—major updates may break compatibility, minor updates add functionality while staying backward-compatible, and patches fix bugs without changing behavior. When you combine semantic versioning with immutable image tags, you ensure that once a version is published, it cannot be altered, so environments that depend on that tag will always get the same artifact. Linking each build to a specific commit further strengthens traceability, letting you identify the exact source state that produced a given artifact and enabling precise audits or rollbacks.

This approach beats other strategies because incremental numbers alone provide little context about impact, date-based versions can be ambiguous about compatibility and upgrade paths, and not versioning at all destroys the ability to reproduce or roll back deployments.