Releases: zktx-io/sui-extension
Releases · zktx-io/sui-extension
v0.3.26
v0.3.24
v0.3.23
Refactor account storage and signing, add canSign checks Introduces schema versioning for account storage and clears old/invalid schemas, requiring re-login if needed. Extracts transaction signing logic to a shared utility, adds a canSignAccount check, and propagates canSign to webviews for improved UI/UX and error handling. Refactors related code to use canSign for enabling/disabling actions, and improves deploy/upgrade UI feedback and timeout handling.
v0.3.22
Update Upgrade.toml button icons and README instructions Replaces the Upgrade.toml button icons in the package card: shows a document icon for saving locally and a clipboard icon for copying to clipboard. Updates the README to clarify button behavior and icon meanings, and notes that the button is disabled if the package is not upgradeable from the current wallet.
v0.3.21
Add Upgrade.toml workflow and UI for package upgrades Introduces support for Upgrade.toml (case-insensitive) to streamline Sui package upgrades. The Package Explorer UI now detects and displays the Upgrade Cap Id, and provides a button to create or copy Upgrade.toml. After publishing or upgrading, Upgrade.toml is automatically created or updated in the workspace. Backend and state management are updated to support these flows, and the README is updated with detailed instructions and UI documentation.
v0.3.20
Add robust project name validation and improve auth flow Introduces a shared validateProjectName function to enforce stricter folder naming rules in moveFiles and workshopFiles commands, preventing invalid or unsafe names. Also ensures the auth code exchange flow always calls the done callback on failure or max retries, improving reliability.
v0.3.19
v0.3.18
Refactor PTB document loading logic in App.tsx PTB documents are now loaded even when no account is present, and new PTB documents are only created for a network if an account exists. This improves the handling of incoming PTB data and document initialization.
v0.3.17
Migrate account storage to VS Code Secrets API Account data is now securely stored using the VS Code Secrets API instead of plaintext global state. Legacy plaintext account data is removed on load, requiring users to re-login if found. The faucet logic now opens the web faucet for testnet and uses the API only for devnet. Added a new OpenExternal command for opening URLs from the webview, and updated content security policies for webviews. Refactored async account loading throughout providers to support the new storage mechanism.