Skip to content

Commit 7c39139

Browse files
committed
new changelog
Signed-off-by: Arthur Mayoux <arthur@getprobo.com>
1 parent 224de48 commit 7c39139

2 files changed

Lines changed: 34 additions & 0 deletions

File tree

203 KB
Loading
Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
---
2+
title: "Vendors Are Now Third Parties"
3+
description: "Vendor is now Third Party across the API, CLI, webhooks, and console — a breaking rename that better matches compliance terminology."
4+
date: 2026-05-15
5+
image: "/changelog/2026-05-15-rename-vendors-third-parties.png"
6+
tags: ["Console"]
7+
---
8+
9+
Probo has renamed the Vendor concept to Third Party everywhere.
10+
11+
This is a breaking change across the full API surface.
12+
13+
## What changed
14+
15+
- GraphQL and MCP: all `vendor*` fields and types renamed to `third_party*`
16+
- Webhook events: `vendor:*` events are now `third_party:*`
17+
- CLI: `prb vendor` command group renamed to `prb third-party`
18+
- Console and Trust page URLs updated accordingly
19+
- Database snapshot type: `VENDORS``THIRD_PARTIES`
20+
21+
## Why it matters
22+
23+
The rename better reflects what the feature tracks: any third-party service your organization uses, not just traditional vendors. It also aligns the product language with GDPR and SOC 2 terminology used by compliance teams.
24+
25+
## What you need to do
26+
27+
If you have automations, scripts, or integrations that use the Probo API or CLI:
28+
29+
- Update webhook listeners from `vendor:*` to `third_party:*`
30+
- Update `prb vendor` calls to `prb third-party`
31+
- Update any hardcoded GraphQL queries or MCP tool calls referencing vendor fields
32+
- Update any saved URLs that include `/vendor` paths
33+
34+
Existing data is migrated automatically. No manual data migration needed.

0 commit comments

Comments
 (0)