Define the new internet.
Look up the words people use online, add the ones we missed, and help make the internet easier to understand.
Look up the words people use online, add the ones we missed, and help make the internet easier to understand.
5,641 definitions
Release Artifact Signature is a devops supply-chain record that proves that an artifact came from an expected build path for versioned delivery of code or content. It uses cryptographic signatures, provenance, and verification so teams can trust deployed packages while keeping evidence, reliability, and public-safe operational boundaries clear.
Release Build Gate is a devops quality gate that blocks promotion when required checks fail for versioned delivery of code or content. It uses tests, lint, security scans, and policy rules so teams can prevent broken releases while keeping evidence, reliability, and public-safe operational boundaries clear.
Release Config Drift Check is a devops consistency check that finds differences between intended and live configuration for versioned delivery of code or content. It uses desired state, live state, and diff reports so teams can avoid surprise environment behavior while keeping evidence, reliability, and public-safe operational boundaries clear.
Release Evidence is a GitOps term for the logs, commits, checks, and status signals that show what changed and why. It helps teams, humans, and agents compare declared source state with running systems, then act without pretending a deployment did more than the evidence shows. Source context: OpenGitOps principles.
Release Freeze is a GitOps term for a period when normal releases are paused to reduce risk. It helps teams, humans, and agents compare declared source state with running systems, then act without pretending a deployment did more than the evidence shows. Source context: OpenGitOps principles.
Release Incident Timeline is a devops response record that orders alerts, actions, and decisions during an incident for versioned delivery of code or content. It uses timestamps, owners, and evidence links so teams can learn from outages without guesswork while keeping evidence, reliability, and public-safe operational boundaries clear.
Release Infra Plan is a devops change preview that shows expected infrastructure changes before apply for versioned delivery of code or content. It uses resource graphs, policy checks, and cost notes so teams can review platform changes safely while keeping evidence, reliability, and public-safe operational boundaries clear.
Release Release Manifest is a devops delivery record that lists versions, artifacts, routes, and checks for a release for versioned delivery of code or content. It uses commit IDs, checksums, and deployment URLs so teams can make releases auditable while keeping evidence, reliability, and public-safe operational boundaries clear.
Release Rollback Plan is a devops recovery plan that defines how to return to a known good version for versioned delivery of code or content. It uses version pins, database notes, and operator steps so teams can recover quickly from bad changes while keeping evidence, reliability, and public-safe operational boundaries clear.
Release Rollout Guard is a devops release control that limits exposure during gradual deployment for versioned delivery of code or content. It uses traffic slices, health checks, and automatic pause rules so teams can reduce blast radius while keeping evidence, reliability, and public-safe operational boundaries clear.