All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
0.7.1 - 2023-11-17
- add
--offline
forsign-with-ledger
option (#260) - Updated legacy command compatibility for near-cli (JS) for dev-deploy, validators, and staking commands (#256)
0.7.0 - 2023-10-31
- New command: staking - delegation (#227)
- Refactored NEAR tokens usages to use a strictly typed near-token crate (#253)
0.6.2 - 2023-10-17
- Exposed some of the functions to use "manage-profile" in bos-cli-rs (#249)
- Exposed subcommands related to "deploy" to reuse in cargo-near (#247)
0.6.1 - 2023-10-09
- Added a new command to manage BOS profile in SocialDB (#231)
- Provide a relevant faucet error message when helper API server returns an error (#243)
- Exposed sponsor_by_faucet_service module to re-use in "cargo-near" (#246)
0.6.0 - 2023-09-28
- New command export-account (#226)
- [breaking] Added system keychain support for windows & linux, so now all major desktop operating systems are supported! (#232)
- order networks selection based on the selected account id (bubble up more relevant networks) (#225)
- CLI must return a non-zero exit code when function call (as-transaction) fails (#238)
- legacy view-function call with --base64 was not recognized (#237)
- self update is now pointing to the right archive name (#234)
- Upgraded cargo-dist to 0.3.0 version to enable MSI Windows installer, and binary artifacts on every PR (#241)
- Switch to near-gas crate (#240)
- New command to view contract storage state (#239)
0.5.2 - 2023-08-17
- Select your account when prompted interactively (#224)
- Allow to specify a custom Web Wallet URL when importing account (default to MyNearWallet) (#218)
- Upgrade cargo-dist to 0.1.0 release (#229)
0.5.1 - 2023-06-07
- New
transaction sign-transaction
command [useful in combination with... sign-later
andtransaction send-signed-transaction
commands] (#215)
- Upgraded NEAR crates to 0.17.0 release (#216)
0.5.0 - 2023-06-05
- New offline mode allows to prepare transactions on devices that are not connected to the Internet (#209)
- Add support for no-args view-function calls for legacy JS CLI
view
command (#213)
0.4.3 - 2023-06-02
- New command to send a signed transaction [potentially constructed offline] (#206)
- Extended access-key deletion with an option to delete multiple keys in a single transaction (#207)
- Updated dependencies to the most recent versions
0.4.2 - 2023-05-26
- Added Json type (#203)
0.4.1 - 2023-05-22
- Added extra space at the beginning of a line in interactive queries (#196)
- Added a guide on
send-meta-transaction
(#192)
0.4.0 - 2023-05-02
- Meta-Transactions support (#189)
- Support for adding key from Ledger hardware wallet (#188)
- fixed call function with non-JSON arguments being incorrectly displayed as
null
(#187) - pass right token to release-plz action (#185)
0.3.5 - 2023-04-21
- Fixed self-update to use the proper archive name generated by cargo-dist
0.3.4 - 2023-04-20
- Enable self-update on CI and NPM installer for binary releases (#183)
- release v0.3.3 (#182)
0.3.3 - 2023-04-20
- Added support for Contract Storage Management Standard (#179)
- update release-plz-action to v0.5 (#180)
0.3.2 - 2023-04-11
- Show contract function call result and make it usable in scripts by only writing the result to stdout, and everything else will be printed to stderr (#177)
- Use optimisticly latest nonce for the access key instead of the final one to avoid errors running commands one after the other (#176)
- fixed printing about saving the access key (#173)
- Added GitHub Actions installation instructions
0.3.1 - 2023-04-06
- Use custom GITHUB_TOKEN to be able to trigger follow up CI jobs
- make a git tag with Release-plz, so it triggers binary release pipeline (#170)
- Renamed
near-cli
binary tonear
as it has special handlers for the commands of near CLI JS, and can be used as a replacement to near CLI JS that will guide users on how to use the new commands when they type the old commands. - Improved continuous integration pipelines to streamline releases (each push to
master
branch will trigger a pipeline that will create a PR suggesting to cut a new release, and once the version is ticked, crate will be published and tagged, and then binary release pipeline will kick in)