Nacos v1.0.1 Release Notes
Release Date: 2019-06-12 // almost 5 years ago-
๐ This version contains several optimizations and bug fixes, and also some important features.
๐ Extended health checker are now supported #359. Thanks to the contribution of @XCXCXCXCX, you can follow the README to build your own health checkers.
โก๏ธ We also introduce a new interface
NamingMaintainService
in #747, which contains methods to update instances and edit services. Thanks to @chuntaojun.Hostname can now be registered in Nacos, the related issue is #963. Thanks to @Albert-Hugo.
The complete list of issues is:
- ๐ [#359] Support user extended health check type
- โก๏ธ [#747] Add create and update service methods in SDK
- ๐ฒ [#827] Nacos Naming's log settings affect the root log
- ๐ [#876] Nacos web management console cannot display cluster node status
- ๐ [#963] Does nacos support to register a instance with host name?
- ๐ง [#1003] Nacos configuration list fuzzy query is invalid
- [#1007] "enabled" and "enable" are Inconsistent
- [#1062] Selector should not select the disable instance
- [#1069] Client beat failed if beat info is too large
- [#1075] NamingEvent add getGroupName and getClusters method
- [#1084] The console adds yaml validator
- [#1091] Healthy server list inconsistent in some situations
- ๐ง [#1118] Historical profile retention time changed from 30 days to configurable
- ๐ [#1148] Windows script cannot specify FUNCTION_MODE
- [#1150] Correct the Relationship between Services and Clusters
- ๐ [#1154] [Feature] Nacos Client supports the update of service instances' metadata
- ๐ฒ [#1215] Nacos heartbeat log is too frequent once a second, it is recommended to change to debug level
- ๐ [#1217] cannot deploy nacos server inside EDAS
- โ [#1227] DomainsManagerTest and RaftStoreTest Don't Work
- ๐ [#1306] Nacos Client Support Multi Enviroment Switch
- [#1308] the judgement that whether server contains ":" should judge every server,not the first one
- ๐ [#1319] Can Nacos support query instances using keyword?
- โก๏ธ [#1334] Always failed when update instance healthy status