Releases: SIMBAChain/truffle
no more AzureHandler
handling .name not found in org and app
this release gives a clearer error message when someone tries to perform noninteractive login, but no organisation or application field are found in their simba.json.
no more v2
If you include /v2 in your SIMBA_API_BASE_URL, an error will now be thrown.
You can also now set your SIMBA_API_BASE_URL in your env file
Fixed error handling (throwing instead of returning errors)
updated documentation
delete contracts, create app from terminal
v3.4.1 minor change
sync command now pull
This release now uses "pull" instead of "sync" for the action of pulling source code from SIMBA Chain and syncing with local project.
Final pre-axios version
This version uses the version of @simbachain/web3-suites that still has some code that implements requests-promise library instead of axios.
new login/logout functionality (from develop)
No breaking changes. login/logout now delete authProviderInfo from simba.json, which should prevent issues with trying to use old/outdated authProviderInfo if someone changes baseURL in their simba.json but forgets to change their authProviderInfo.
updated version to handle variable JSON objects for auth info
v2.1.1 updated web3-suites
v2.0.0
This is version 2.0.0 of the SIMBA Chain Truffle plugin.
This version introduces breaking changes, regarding auth flow. This version of the plugin uses keycloak device login, and thus the fields in the user's simba.json are going to look different than in v1.
The deployment process has also been streamlined, to allow for greater ease when it comes to both exporting and deploying contracts to simbachain.com using the plugins.
Also, much of the code that originally lived in this codebase now lives in https://github.com/SIMBAChain/web3-suites-common. That's because SIMBA's family of web3 plugins has grown, and now includes Hardhat. So code that is utilized by both of those plugins now lives in that common repo.
new login/logout functionality
No breaking changes. login/logout now delete authProviderInfo from simba.json, which should prevent issues with trying to use old/outdated authProviderInfo if someone changes baseURL in their simba.json but forgets to change their authProviderInfo.