feat(backup): support incremental backups via baseBackupId

[gkampitakis]

What

Weaviate accepts incremental_base_backup_id on POST /v1/backups/{backend} to build a file-based incremental backup on top of an existing one (added in weaviate#10275, released in 1.34.18 / 1.35.13 / 1.36.3 / 1.37.0). The client had no way to set it, and dropped the field from list/status responses, so incremental backups were unreachable from TypeScript.

This mirrors the Go v6 client, which exposes it as a top-level CreateOptions.BaseBackupID (not nested under config) and surfaces Info.BaseBackupID on returned backups.

Changes

• client.backup.create and collection.backup.create accept an optional baseBackupId, via the new BackupCreateArgs / BackupCollectionCreateArgs types. Restore args are untouched — the field is create-only, as in Go.
• BackupCreator.withBaseBackupId() puts it on the request as incremental_base_backup_id.
• BackupStatusReturn gains baseBackupId; getCreateStatus and list map incremental_base_backup_id onto it.

All additive — no existing signature changes meaning, and BackupCreateArgs is a superset of BackupArgs<BackupConfigCreate>.

Notes

• Weaviate only returns incremental_base_backup_id to callers it has confirmed as root users, so baseBackupId is often absent on reads even when the backup is incremental. Documented on the type.
• The server validates the base: it must exist, be SUCCESS, be strictly older, share the same compression type, and the whole ancestor chain is walked for cycles. No client-side duplication of that.

Testing

• test/collections/backup/mock.test.ts: asserts the create request carries incremental_base_backup_id (and omits it for a full backup), and that status/list responses map it to baseBackupId.
• test/collections/backup/integration.test.ts: full backup → insert more data → incremental backup on that base → restore → assert both objects are present. Also asserts an unknown base is rejected. Gated with requireAtLeast(1, 34, 18).

Verified locally against Weaviate 1.36.10: all backup mock + integration tests pass. npm run lint, npm run format:check and npm run docs are clean (no new warnings).

🤖 Generated with Claude Code

https://claude.ai/code/session_01NZ2p2CzXLS92ThnvDjnxAE

[orca-security-eu]

Orca Security Scan Summary

Status	Check	Issues by priority
Passed	Infrastructure as Code	0   0   0   0	View in Orca
Passed	SAST	0   0   0   0	View in Orca
Passed	Secrets	0   0   0   0	View in Orca
Passed	Vulnerabilities	0   0   0   0	View in Orca

[bevzzz]

@gkampitakis I think this is a duplicate of #459

[gkampitakis]

@gkampitakis I think this is a duplicate of #459

🙈 Should have checked first, sorry @bevzzz . Closing it over #459