[PLAT-9426] Update to latest spec

[jdm717]

Summary

Updates to the latest OpenAPI spec, primarily to pull in changes around the sourceSuppliedIdStrategy for scene-item creation. Some other notable changes in this version:

• Adds support for creating a scene-item from another scene-item as a source
• Adds support for reparenting a scene-item by updating its parent relationship
• Adds root-level endpoint configuration for an account's oidc_userinfo_endpoint
• Adds the and, or, and not filter expressions
• Adds support for filter expressions on a number of resource endpoints (files, file collections, parts, scene items, scene alterations, and thread participants)
• Renames a number of property-key-policy related endpoints, renaming from types / methods like PropertyKeyPolicyEntryList to PropertyKeyList
  • I don't know of any usage of this, and this API isn't currently exposed on the VertexClient object, so this shouldn't be a concerning breaking change

In total, there were a couple breaking changes with this version, so it's been bumped up to v0.45.0:

• Property-key-policy renames as mentioned above
• File collection supplied ID filtering has been changed to use a FilterExpression instead of a comma separated list

Test Plan

• Verify the above features are available in the newly published version

Release Notes

N/A

Possible Regressions

N/A

Dependencies

N/A

---

Note

Medium Risk
Breaking TypeScript API renames and file-collection filter signature changes can break compile-time callers; account OIDC endpoint and scene-item copy/reparent behavior affect auth and scene graph workflows.

Overview
Bumps the package to v0.45.0 and regenerates the OpenAPI client from an updated spec.yml, reflecting a broad Vertex API surface refresh.

Scene items can use another scene-item as a relationships.source (copy across scenes), optional sourceSuppliedIdStrategy (preserve / clear / replace-or-add-prefix) for child supplied IDs, and reparenting via relationships.parent (including null for scene root). List scene-items gains filter[name] with expression or literal forms.

Accounts expose optional oidc_userinfo_endpoint on create, read, and update (nullable on update to clear). Applications can update scopes; create-application typing shifts to AdminCreateApplicationRequestData.

Filtering expands: FilterExpression adds and / or / not and FilterExpressionOrLiteral; name filters land on files, parts, and scene-items; file collections move from CSV supplied-ID filtering to expression-based name, suppliedId, createdAt filters plus sort (name / created).

Property-key policies are a breaking reshape: /entries becomes /property-key-policies/{id}/keys with renamed client methods (*PropertyKeyPolicyKeys*), PropertyKeyList responses, and PropertyEntryKey in upsert payloads instead of entry wrapper types.

Smaller contract fixes: pagination on thread participants and scene-view scene-alterations; deprecated queued-translations documented as 301 redirect; getUserGroup returns UserGroup; queued scene-sync completion may redirect to scene-sync.

^{Reviewed by Cursor Bugbot for commit f6d287a. Bugbot is set up for automated code reviews on this repo. Configure here.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit f6d287a. Configure here.}

[cursor]

Filter expressions do not serialize

High Severity

Passing a FilterExpression as filterName, filterSuppliedId, or filterCreatedAt assigns the object to the query map, and setSearchParams stringifies it as [object Object]. The client never emits the documented filter[name][contains]=... form, so the new file-collection, parts, and scene-item filters fail at runtime. File-collection params also omit FilterExpressionOrLiteral, so a string fallback is not available either.

Additional Locations (2)

• api.ts#L24433-L24436
• api.ts#L30503-L30506

 

^{Reviewed by Cursor Bugbot for commit f6d287a. Configure here.}