Releases: elastos/Elastos.Hive.Node
Releases · elastos/Elastos.Hive.Node
pre-v2.9.2.2
Release Notes:
- Refine the process to get file from IPFS proxy by CID.
- Refine the backup process to add application did.
v2.9.2
Release Notes:
- Rename the pricing plan of the payment service.
- Add API to get user's scripts.
- Add access information on the applications and the vault.
- Add memory and storage details on the node information.
- Add a
force
parameter on the unsubscribe vault API. - Update eladid_wrapper to align with
DID native SDK
. - Refine the parameter check of calling script by URL.
- Support getting the collections by the database service.
- Restrict to operate the internal collections of the database.
- Refine the logic of uploading the anonymous file.
- Add restriction to the database and script which is for internal use.
- Refine database, files, scripting services.
- Other improvements and bug fixes.
Here is the deployment guide for a new node.
v2.9.1
Release Notes:
- Support encryption on the backup & restore process.
- Refine the config item names of the
.env
file. - Refine the implementation of services: subscription, files, provider, backup, etc.
- Refine the files service API to add properties to the file metadata:
is_encrypt
andencrypt_method
. - Refine
params
checking when calling a script. - Refine to remove unused codes on v2 APIs.
- Refine the database updating and finding operations to support empty
filter
.
Here is the deployment guide for a new node.
v2.8.1
Release Notes (2.8.1):
- Integrated a new version of payment mechanism with smart contract supported ;
- Improved backup implementation to provide stable backup service;
- Supported anonymous data access without requiring user DID and application DID under scripting rules;
- Supported $params and possible to return "total" value as a result of "find" type scripting.
- Improved access token cache implementation;
- Refined storage used amount on files and database data;
- Provided more APIs to get information related to vault/backup service
- Resolved the issue of inconsistency for "nbf" field in Credentials between applications and Hive node;
- Other improvements and bug fixes.
Here is the deploy guide for a new node.
v2.7.2 (Hotfix)
Release Notes (Hotfix):
- Fix an issue about operating the document containing '$' sign on v1 APIs.
v2.7.1
v2.6.1
Release Notes:
- Normalize and improve the content of items in the Hive node environment file (.env)
- Change to use exported private did-store in base58 string instead of explicit mnemonic in environment file (.env)
- Add the ownership declaration into the config file .env and provide APIs to fetch information related to the ownership of the node;
- More APIs to get public information from Hive node;
- Refine condition to catch/collect logs to the Sentry platform with the least edge cases;
- New APIs to get a list of used-app information in the owned vault
- Use the restful flask framework to replace the original customized one;
- More internal implementation improvement;
Here is the deploy guide for a new node.
v2.5.1
ChangeLogs:
- Improvement on log/error messages output implementation;
- Support with ProviderService to fetch all vault metadata on the Hive node;
- Support to insert key with $ (dollar) as scripting content;
- Bugfix for using multiple conditions in the scripting mechanism
- API docs refinement
- Other internal bugfixes and improvements.
Here is the deploy guide for a new node.
v2.4.1
Release Notes for the New Version:
- Improved HTTP RESTful APIs and internal implementation;
- IPFS integrated as internal storage for data;
- Refactored the Files module with IPFS nodes;
- Refactored the backup/restore module with IPFS network;
- More test cases to cover verification.
To deploy the hive node, please check the attachment deployment-guide.md.
To upgrade from the preview version, please check the document upgrade_to_v2.4.1.md.
v2.3.1
Release Notes for the New Version:
- Support a verifiable payment mechanism;
- Support mongo atlas.
- Support the CORS option on the configure file.
- Support update or delete one on the v2 database APIs.
- Add documents for the v2 APIs.
- Add the v2 about APIs.
- Refine the v2 backup APIs.
- Fix bug for counting storage usage about the v1 files API.
- Test cases improvement.