Skip to content

Latest commit

 

History

History
55 lines (41 loc) · 2.18 KB

File metadata and controls

55 lines (41 loc) · 2.18 KB

Changelog

All notable changes to sorokit-core will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[Unreleased]

Added

  • Initial public release of sorokit-core
  • Framework-agnostic TypeScript SDK for Stellar wallet connection, transactions, and Soroban contract interaction
  • wallet module for connecting and disconnecting wallets, signing transactions via SWK adapters
  • account module for fetching account info, balances, and streaming account state
  • transaction module for building, submitting, and tracking transactions; fee estimation; and transaction streaming
  • soroban module for reading and invoking Soroban smart contracts
  • network module for configuration of mainnet, testnet, and futurenet
  • No-throw result model (SorokitResult<T>) for all operations
  • Support for Freighter, XBull, and Lobstr wallet adapters
  • Async generator-based streaming for accounts and transactions
  • Testing utilities with mock client and mock wallet adapter
  • Comprehensive TypeScript types for all operations
  • ESLint and TypeScript configuration for code quality
  • Vitest test suite with coverage
  • validateDeployConfig, collectDeployConfigIssues, and formatDeployConfigIssues for pre-flight validation of contract deployment configuration, reporting every missing or malformed value with an actionable fix (#356)
  • examples/router-swap — frontend reference for router integration covering quote retrieval, swap execution, and transaction tracking (#357)
  • npm run typecheck:examples to type-check bundled examples against the SDK source

Fixed

Changed

  • buildContractDeploy validates its configuration before contacting the network and returns INVALID_CONFIG with per-field guidance instead of an opaque RPC or SDK error (#356)

Deprecated

Removed

Security


Release History

Versions will be documented here as they are released following Semantic Versioning conventions.

Format:

  • [Version] - YYYY-MM-DD: Release date and notes
  • Sections: Added, Changed, Fixed, Deprecated, Removed, Security