main changes are using @turnkey/sdk-server instead of @turnkey/http + @turnkey/api-key-stamper for the backend routes. see https://docs.turnkey.com/sdks/migration-path for migration paths
A previous attempt was made in https://github.com/tkhq/sdk/pull/413 , but ultimately it seems premature to make some of the changes included in that diff.
How I Tested These Changes
Local
Did you add a changeset?
If updating one of our packages, you'll likely need to add a changeset to your PR. To do so, run pnpm changeset. pnpm changeset will generate a file where you should write a human friendly message about the changes. Note how this (example) includes the package name (should be auto added by the command) along with the type of semver change (major.minor.patch) (which you should set).
These changes will be used at release time to determine what packages to publish and how to bump their version. For more context see this comment.
Summary & Motivation
$title
main changes are using
@turnkey/sdk-server
instead of@turnkey/http + @turnkey/api-key-stamper
for the backend routes. see https://docs.turnkey.com/sdks/migration-path for migration pathsA previous attempt was made in https://github.com/tkhq/sdk/pull/413 , but ultimately it seems premature to make some of the changes included in that diff.
How I Tested These Changes
Did you add a changeset?
If updating one of our packages, you'll likely need to add a changeset to your PR. To do so, run
pnpm changeset
.pnpm changeset
will generate a file where you should write a human friendly message about the changes. Note how this (example) includes the package name (should be auto added by the command) along with the type of semver change (major.minor.patch) (which you should set).These changes will be used at release time to determine what packages to publish and how to bump their version. For more context see this comment.