Skip to content

Document removal of children response field in GET /v1/project #130

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nscuro merged 1 commit into from
Jun 5, 2026
Merged

Document removal of children response field in GET /v1/project #130

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/reference/api/v5-breaking-changes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -228,6 +228,11 @@ v5 removes the `POST` and `DELETE` variants of `/v1/policy/{policyUuid}/tag/{tag
- **Enum values removed**: `Project.classifier.NONE`, `Project.collectionLogic.NONE`. `null` or an absent field means
what `NONE` meant in v4.

**`GET /v1/project`**

- **Removed response field**: `Project.children` inline array. Fetch project children via
`GET /v1/project/{uuid}/children` instead.

**`POST /v1/project/batchDelete`**

- **Removed response**: v4 documented a `400` with `ProjectOperationProblemDetails`. v5 documents only `204` and `401`.
Expand Down