[github-actions]

Breaking changes

Changes that can break typed code. They mirror the API, so they ship in a minor release, and the release notes list them under "API changes that can break typed code" (docs/DESIGN.md sections 3.1 and 13).

None detected.

Release

feat(spec): this sync changes what a caller can observe, so merging it releases a minor version.

Checks run by the sync

Step	Result
Regenerate: python3 codegen/generate.py	success
Build: dotnet build Didit.sln -c Release	success
Test: dotnet test on net8.0	success

Upstream API spec sync (docs/DESIGN.md section 3.1), generated by codegen/spec_sync.py.

File	Upstream	SHA-256
openapi/verification.json	https://docs.didit.me/openapi-25.json	unchanged (62595c19d8b0)
openapi/account.json	https://docs.didit.me/openapi-auth.json	3ebf65c96688 to c4dc0eb6b916
openapi/authentication.json	https://docs.didit.me/openapi-authentication.json	unchanged (3987984647bf)

Operations

Added (0)

None.

Removed (0)

None.

Changed (1)

• account POST /organizations/me/{org_id}/applications/: account.applications.create

Schemas

Added (0)

None.

Removed (0)

None.

Changed (1)

• ApplicationDataLocation (account)

---

Release notes

release-please reads the block below instead of the merge commit, so the release type (feat(spec)) and its notes do not depend on how the commit is titled. Merge with Squash and merge: with a merge commit release-please reads the block once per commit and every line appears twice in the release notes. Keep the block when you edit this description.

BEGIN_COMMIT_OVERRIDE
feat(spec): sync API spec 2026-11-10
END_COMMIT_OVERRIDE