October 1–6, 2026 brought a pair of releases for the Veracode community: a new dependency graph view in BetaUI and the latest GitLab Workflow Integration update. Here's what shipped and why it matters.

Dependency Graph in BetaUI

Released October 1, 2026

A new dependency graph is now available in BetaUI, giving teams a visual view of direct and transitive dependencies — the libraries an application relies on, plus the libraries those libraries pull in. The graph works for both Upload & Scan and Agent-based scans, making it easier to understand the full supply chain behind a project. One limitation to note: the dependency graph is available only for new scans performed on or after October 1, 2026.

GitLab Workflow Integration v2.1.9

Released October 6, 2026

GitLab Workflow Integration v2.1.9 is now live. This release adds support for the predependency_command parameter in veracode.yml, which lets teams run single-line or multiline commands before Veracode packages the project. It also adds support for the policy parameter under veracode_iac_secrets_scan: in veracode.yml, enabling Infrastructure-as-Code (IAC) scans to run with policy. A new feature blocks any merge request from merging when break_build_policy_findings and break_build_on_error are set to true, helping teams keep policy-violating code out of protected branches. SCA (Software Composition Analysis) scans in GitLab workflows have also been optimized. Release notes are available here, with documentation updates to follow.

For the full set of Veracode release notes, visit https://docs.veracode.com/updates/.