feat: support addressing objects by versionId

[TylerHillery]

What kind of change does this PR introduce?

Feature

What is the current behavior?

Currently we don't allow users to specify version id

What is the new behavior?

Can now pin get, head, info, sign, copy, move, delete, and deleteObjectets to a specific object version via versionId. Also added additional indexes.

Additional context

Left out S3 API changes for now as well. Will be done in a follow up PR.

Only one version can exist per object today, so versionId just reselects the same object you'd already get by default but this lays groundwork for real multi-version support later.

[Copilot]

Pull request overview

Adds API-level and storage-layer support for pinning object operations to a specific object version via versionId / sourceVersionId, laying groundwork for multi-version objects while keeping current behavior intact.

Changes:

• Extend object routes (get/head/info, signed URLs, copy/move, delete) to accept a version identifier and pass it through to storage lookups.
• Update storage/database lookup and update paths to optionally filter by version, and include versionId in signed download tokens.
• Add new tenant migration indexes to support version-aware addressing and future versioning constraints.

Reviewed changes

Copilot reviewed 17 out of 17 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
src/test/object.test.ts	Adds integration tests covering version-pinned get/info/public get/copy/move/delete and signed URL flows.
src/storage/object.ts	Plumbs optional version IDs through findObject, deleteObject, copyObject, moveObject, and signed URL creation.
src/storage/database/pg.ts	Extends findObject and updateObject queries to optionally constrain by version.
src/storage/database/adapter.ts	Updates the Database interface to accept optional version parameters for findObject and updateObject.
src/internal/database/migrations/types.ts	Registers new migration IDs for added object/version indexes.
src/internal/auth/jwt.ts	Extends SignedToken to optionally carry versionId.
src/http/routes/object/moveObject.ts	Accepts sourceVersionId and forwards it to storage move operation.
src/http/routes/object/getSignedURL.ts	Accepts versionId for signed URL generation and forwards it to storage signing.
src/http/routes/object/getSignedObject.ts	Uses versionId from verified token to fetch the pinned object version before rendering.
src/http/routes/object/getPublicObject.ts	Accepts versionId query param and passes it to object lookup.
src/http/routes/object/getObjectInfo.ts	Extends query schema and passes versionId to object info lookup.
src/http/routes/object/getObject.ts	Accepts versionId query param and passes it to object lookup.
src/http/routes/object/deleteObject.ts	Accepts versionId query param and forwards it to storage delete operation.
src/http/routes/object/copyObject.ts	Accepts sourceVersionId and forwards it to storage copy operation.
migrations/tenant/0064-objects-key-version-index.sql	Adds a unique index on (bucket_id, name, version) to support version addressing.
migrations/tenant/0065-objects-current-version-index.sql	Adds a unique index enforcing a single current (unarchived) row per (bucket_id, name).
migrations/tenant/0066-objects-null-version-index.sql	Adds a unique partial index for non-versioned objects keyed by (bucket_id, name).

Suppressed comments (1)

src/storage/database/pg.ts:1191

• version is gated by a truthy check, so a provided empty string (e.g. ?versionId=) would be ignored and the lookup would fall back to the unpinned object. Use an undefined check so any provided value participates in the WHERE clause.

    if (version) {

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[coveralls]

Coverage Report for CI Build 32666241045

Coverage increased (+0.04%) to 81.203%

Details

• Coverage increased (+0.04%) from the base build.
• Patch coverage: 68 of 68 lines across 14 files are fully covered (100%).
• No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	13160
Covered Lines:	11113
Line Coverage:	84.45%
Relevant Branches:	7827
Covered Branches:	5929
Branch Coverage:	75.75%
Branches in Coverage %:	Yes
Coverage Strength:	612.48 hits per line

---

💛 - Coveralls