### 1.0.3

Release notes

### Seata-go 1.0.3 Seata-go 1.0.3 Released. Seata-go is an easy-to-use, high-performance, open source distributed transaction solution. The version is updated as follows: ### feature： - [[#380](https://github.com/apache/incubator-seata-go/pull/380)] support xa mysql connection - [[#383](https://github.com/apache/incubator-seata-go/pull/383)] support read tcc fence configuration file - [[#389](https://github.com/apache/incubator-seata-go/pull/389)] add the transaction id of xa mode - [[#398](https://github.com/apache/incubator-seata-go/pull/398)] support read TM configuration file - [[#399](https://github.com/apache/incubator-seata-go/pull/399)] support read getty configuration file - [[#405](https://github.com/apache/incubator-seata-go/pull/405)] support at mode insert on duplicate sql parsing - [[#406](https://github.com/apache/incubator-seata-go/pull/406)] support read transport configuration file - [[#410](https://github.com/apache/incubator-seata-go/pull/410)] support read undo log configuration file - [[#411](https://github.com/apache/incubator-seata-go/pull/411)] use tm's profile properties in the project - [[#412](https://github.com/apache/incubator-seata-go/pull/412)] support read rm configuration file - [[#412](https://github.com/apache/incubator-seata-go/pull/412)] support read service configuration file - [[#419](https://github.com/apache/incubator-seata-go/pull/419)] use undo-log's profile properties in the project ### bugfix： - [[#387](https://github.com/apache/incubator-seata-go/pull/387)] fix loop recursion problem in OpenConnector - [[#401](https://github.com/apache/incubator-seata-go/pull/401)] fix branch register process - [[#418](https://github.com/apache/incubator-seata-go/pull/418)] fix the configuration file problem of undo log - [[#423](https://github.com/apache/incubator-seata-go/pull/423)] fix getty initialization failure - [[#424](https://github.com/apache/incubator-seata-go/pull/424)] fix getty initialization failure - [[#429](https://github.com/apache/incubator-seata-go/pull/429)] fix the problem of execution failure in at mode ### optimize: - [[#366](https://github.com/apache/incubator-seata-go/pull/366)] add data check before rollbeck - [[#367](https://github.com/apache/incubator-seata-go/pull/367)] simplify to make codes more readable - [[#369](https://github.com/apache/incubator-seata-go/pull/369)] remove unless function - [[#385](https://github.com/apache/incubator-seata-go/pull/385)] optimize the SQL used in AT sample - [[#388](https://github.com/apache/incubator-seata-go/pull/388)] optimize comments and dead code - [[#390](https://github.com/apache/incubator-seata-go/pull/390)] optime rm init - [[#392](https://github.com/apache/incubator-seata-go/pull/392)] optimize code style - [[#394](https://github.com/apache/incubator-seata-go/pull/394)] optimize at mode base executor - [[#400](https://github.com/apache/incubator-seata-go/pull/400)] optime protocol init - [[#408](https://github.com/apache/incubator-seata-go/pull/408)] optime log init - [[#409](https://github.com/apache/incubator-seata-go/pull/409)] refactor logic of delete and insert sql in at mode - [[#414](https://github.com/apache/incubator-seata-go/pull/414)] rename unit test file - [[#422](https://github.com/apache/incubator-seata-go/pull/422)] remove unused config code ### test: ### doc: - [[#417](https://github.com/apache/incubator-seata-go/pull/417)] optiomize readme file ### contributors: Thanks to these contributors for their code commits. Please report an unintended omission. - [AlexStocks](https://github.com/AlexStocks) - [luky116](https://github.com/luky116) - [georgehao](https://github.com/georgehao) - [lxfeng1997](https://github.com/lxfeng1997) - [106umao](https://github.com/106umao) - [liiibpm](https://github.com/liiibpm) - [wang1309](https://github.com/wang1309) - [iSuperCoder](https://github.com/iSuperCoder) - [jasondeng1997](https://github.com/jasondeng1997) - [Charlie17Li](https://github.com/Charlie17Li) - [Code-Fight](https://github.com/Code-Fight) - [Kirhaku](https://github.com/Kirhaku) Also, we receive many valuable issues, questions and advices from our community. Thanks all.