v3.0.1-beta.1
Changelog
New Features
- 0e43b64: feat: add build (@cubxxw)
- 2ec3888: feat: add docker file and version appoint (@cubxxw)
- 3cae4e6: feat: add file: (#648) (@cubxxw)
- 643e081: feat: add file: (#650) (@cubxxw)
- ecfbe68: feat: add go release (@cubxxw)
- ab48eda: feat: add go release (@cubxxw)
- 8a87ba6: feat: add test format (@cubxxw)
Bug fixes
- ad91379: fix: Compatible with wasm s3 oss header Date (#630) (@withchao)
- 9ef94ad: fix: StringValue When there are double quotes in the string value, serialization and deserialization fail (#646) (@withchao)
- 9db61be: fix: actions milestones auto (#638) (@cubxxw)
- 00b4483: fix: actions milestones auto (#640) (@cubxxw)
- f940610: fix: actions milestones auto (#642) (@cubxxw)
- 8178564: fix: delete batch build all file (#561) (@cubxxw)
- 0d6034d: fix: fix github auto gh pr (@cubxxw)
- 166fb3c: fix: http redirect compatibility (#659) (@withchao)
- 7ee40bd: fix: init grpc conn multiple in one process will cause zero address when rpc is called (#604) (@wangchuxiao-dev)
- 222d061: fix: msg destruct not effect and notification self 2 self push twice (#596) (@wangchuxiao-dev)
- 4629b03: fix: optimize minio initialization (#602) (@withchao)
- b47d2c5: fix: release 3.0 (@kubbot)
- b95420e: fix: s3 browser preview (#580) (@withchao)
- bc6e0e8: fix: script v3.0 (@kubbot)
- 5cb5de4: fix: user app_manger_level (#584) (@withchao)
Build process updates
- 46ecd91: build: add build copyright admin (@cubxxw)
- 4ea62d6: build: fix chat docker images (@kubbot)
Other work
- 459c68b: Add files via upload (@skiffer-git)
- 94dfea5: Add files via upload (@skiffer-git)
- 68f3f1f: Delete auto-release.yml (#651) (@cubxxw)
- cb59f05: Replace WeChat image links with COS (Cloud Object Storage) (@skiffer-git)
- 36e2025: Update and rename golangci-link.yml to golangci-lint.yml (#637) (@kubbot)
- 73b8f5d: Update cla.yml (#634) (@kubbot)
- 791c3b7: docs: design documentation and deployment devops flow (@cubxxw)
- f3bb890: docs: fix lint update CONTRIBUTING.md (#632) (@EthanForAi)
- 5a7084a: fix bug: grpc options duplicated when send msg (#628) (@wangchuxiao-dev)
- edd6a86: fix bug: obtain user online status err(#567) (#592) (@BanTanger)
- 6de9995: parameter range error (#606) (@hanzhixiao)
- f80e2e3: update readme: With the release of the new system, the readme is also updated accordingly. (@skiffer-git)
- 1552a77: update readme: With the release of the new system, the readme is also updated accordingly. (@skiffer-git)
- 3483296: update readme: With the release of the new system, the readme is also updated accordingly. (@skiffer-git)
- 1f4aefa: update readme: With the release of the new system, the readme is also updated accordingly. (@skiffer-git)
- 2a0d69b: update readme: With the release of the new system, the readme is also updated accordingly. (@skiffer-git)
- 159c81a: update readme: With the release of the new system, the readme is also updated accordingly. (@skiffer-git)
- c2a848a: update readme: With the release of the new system, the readme is also updated accordingly. (@skiffer-git)
Full Changelog: v3.0.0...v3.0.1-beta.1
Helping out
This release is only possible thanks to all the support of some awesome people!
Want to be one of them?
Contributions to this project are welcome! Please see CONTRIBUTING.md for details.
Contact Us
We value close connections with our users, developers, and contributors here at OpenIMSDK. With a large community and maintainer team, we're always here to help and support you. Whether you're looking to join our community or have any questions or suggestions, we welcome you to get in touch with us.
Our most recommended way to get in touch is through Slack. Even if you're in China, Slack is usually not blocked by firewalls, making it an easy way to connect with us. Our Slack community is the ideal place to discuss and share ideas and suggestions with other users and developers of OpenIMSDK. You can ask technical questions, seek help, or share your experiences with other users of OpenIMSDK.
In OpenIM community is recruiting new members! discussion please leave your information, convenient we will better developers around the small gift to send to your hands.
In addition to Slack, we also offer the following ways to get in touch:
- : We also have Slack channels for you to communicate and discuss. To join, visit https://slack.com/ and join our 👀 Open-IM-Server slack team channel.
- : Get in touch with us on Gmail. If you have any questions or issues that need resolving, or any suggestions and feedback for our open source projects, please feel free to contact us via email.
- : Read our blog. Our blog is a great place to stay up-to-date with Open-IM-Server projects and trends. On the blog, we share our latest developments, tech trends, and other interesting information.
- : Add Wechat and indicate that you are a user or developer of Open-IM-Server. We will process your request as soon as possible.
Whether you're looking to join our community or have any questions or suggestions, we welcome you to get in touch with us.