Skip to content

docs: clarify SDK 2.1 compatibility #97

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Seranged wants to merge 2 commits into
base: main
Choose a base branch
from
Open

docs: clarify SDK 2.1 compatibility #97

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1e41010
docs: clarify SDK 2.1 compatibility
Seranged Aug 26, 2026
1a3e83c
docs: correct SDK 2.1 interface requirements
Seranged Aug 26, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 6 additions & 5 deletions packages/euler-v2-sdk/RELEASE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,12 +4,13 @@

Git tags and GitHub Releases are the release-note source of truth. Do not add package-local changelog or release-notes files for new SDK releases.

## PR #96 release classification
## SDK 2.1 compatibility

PR #96 is an intentional breaking SDK release and must be published under a new
major version. Its required Pyth `publishTimes` evidence and required
`IExecutionService` / `IPositionMigrationService` additions are not backward
compatible. Do not publish these changes under a minor or patch version.
SDK 2.1 requires feed-aligned Pyth `publishTimes` evidence, includes
materialized-execution methods on `IExecutionService`, and includes
`prepareMigrationAuthorizationSlots` on `IPositionMigrationService`. Custom
interface implementations and custom Pyth prefetch payloads must implement
their respective SDK 2.1 contracts.

## Release inputs

Expand Down