v1.0.1-beta.1
Changelog
New Features
- 3f10c28: feat: add chat to readme (@cubxxw)
- 3f93b3a: feat: add code file (@cubxxw)
- 5cdd21e: feat: add fix script (@cubxxw)
- f27661b: feat: add go relase (@cubxxw)
- 8b2d583: feat: add go relase (@cubxxw)
- 2ce44dc: feat: add go relase (@cubxxw)
- ed25427: feat: add go relase (@cubxxw)
- 71dce20: feat: add openim test (@cubxxw)
- 82892f4: feat: add windows fix platform (@cubxxw)
- f208815: feat: build ci (@cubxxw)
- 17ec096: feat: build ci (@cubxxw)
- b1b3edb: feat: build ci (@cubxxw)
- 3435527: feat: modify scripts/*.sh (#26) (@AllianceTing)
- c18bbc9: feat: release v1.0.1 (@cubxxw)
Bug fixes
- a7e0281: fix: build platform (@cubxxw)
- 8776ea0: fix: chat release path (@cubxxw)
- f43ca24: fix: fix readme file (@cubxxw)
- 1aa02e2: fix: sql injection risk (#56) (@withchao)
Other work
- 542994e: Email (#45) (@hanzhixiao)
- 323472a: add parameter check (@hanzhixiao)
- c99ef35: reconstruct some rpc (#28) (@hanzhixiao)
Full Changelog: v1.0.0...v1.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.
Get Involved with OpenIM!
Here are some ways to get involved with the OpenIM community:
📢 Slack Channel: Join our Slack channels for discussions, communication, and support. Click here to join the chat Slack team channel.
📧 Gmail Contact: If you have any questions, suggestions, or feedback for our open-source projects, please feel free to contact us via email.
📖 Blog: Stay up-to-date with OpenIM-Server projects and trends by reading our blog. We share the latest developments, tech trends, and other interesting information related to OpenIM.
📱 WeChat: Add us on WeChat (QR Code) and indicate that you are a user or developer of chat. We'll process your request as soon as possible.
Remember, your contributions play a vital role in making OpenIM successful, and we look forward to your active participation in our community! 🙌