Palantir SDK and Application Upgrade

Overview

Treat generated OSDK changes and official Platform SDK releases as contract migrations. Freeze the old and new artifacts, read the relevant migration guide or release notes, update one boundary, and prove compatibility in a non-production environment.

Prerequisites

• Identify the current and target package/product versions, generated Developer Console application, language/runtime, call sites, owners, and target environments.
• Capture lockfiles, generated metadata, OAuth restrictions, tests, representative queries/Actions, and prior product or image version.
• Read references/official-docs.md and the language-specific migration guide or official release history.
• Prepare a branch and non-production installation with a documented downgrade.

Current Contract

• Generated OSDK packages are tied to selected Ontology resources and compatible client versions.
• TypeScript OSDK migration guides document syntax changes for object access, Actions, batch Actions, and Functions/queries.
• Official Platform SDK repositories publish immutable releases and generated API changes.
• DevOps/Marketplace release management can promote and roll back versioned products across environments.