​

Releases and versioning

• Metadata for exact values such as commit SHA, release version, deployment id, or prompt version.
• Tags for broad rollout labels such as canary, stable, release-candidate, or v2-agent.

​

Send version metadata

await capture(
  "support-agent-turn",
  async () => agent.run(userMessage),
  {
    metadata: {
      release: "checkout-release",
      commitSha: process.env.GIT_COMMIT_SHA,
      deploymentId: process.env.DEPLOYMENT_ID,
      promptVersion: "support-prompt",
    },
  },
)

capture(
    "support-agent-turn",
    lambda: agent.run(user_message),
    {
        "metadata": {
            "release": "checkout-release",
            "commit_sha": os.environ.get("GIT_COMMIT_SHA"),
            "deployment_id": os.environ.get("DEPLOYMENT_ID"),
            "prompt_version": "support-prompt",
        },
    },
)

​

Send rollout tags

await capture(
  "support-agent-turn",
  async () => agent.run(userMessage),
  {
    tags: ["canary", "v2-agent"],
  },
)

capture(
    "support-agent-turn",
    lambda: agent.run(user_message),
    {
        "tags": ["canary", "v2-agent"],
    },
)

​

Use versions in Latitude

• search for behaviours introduced by a release
• filter traces by prompt version or deployment id
• compare signal examples before and after a rollout
• scope saved searches to canary traffic
• monitor whether a signal you fixed comes back in a new version

​

Related

• Tags: Track rollout labels
• Metadata: Track exact release fields
• Search: Discover version-specific behaviours
• Signals: Track failure modes across releases