v3.3.3-rc.0

Welcome to the v3.3.3-rc.0 release of OpenIM!🎉🎉!

We are excited to release v3.3.3-rc.0, Branch: https://github.com/openimsdk/open-im-server/tree/v3.3.3-rc.0 , Git hash [363deff], Install Address: https://github.com/openimsdk/open-im-server/releases/tag/v3.3.3-rc.0

Learn more about versions of OpenIM:

• We release logs are recorded on ✨CHANGELOG

• For information on versions of OpenIM and how to maintain branches, read 📚this article

• If you wish to use mirroring, read OpenIM's 🤲image management policy

Want to be one of them 😘?

Note
@openimbot and @kubbot have made great contributions to the community as community 🤖robots(@openimsdk/bot), respectively.
Thanks to the @openimsdk/openim team for all their hard work on this release.
Thank you to all the 💕developers and contributors, people from all over the world, OpenIM brings us together
Contributions to this project are welcome! Please see CONTRIBUTING.md for details.

Changelog

New Features

• abf8e37: feat: Add the help chart script to support k8s deployment (#1145) (@xuexihuang)
• 8a54e46: feat: Add unit test for DeleteGroupMemberHash meth (#1200) (@sweep-ai[bot])
• 1c1f2a9: feat: Add unit test for RemoveRepeatedElementsInLi (#1223) (@sweep-ai[bot])
• b3d2f3b: feat:order logs by time desc (#1250) (@CNCSMonster)

Bug fixes

• 81cc1f3: fix: after modifying the avatar, offline users who joined the group did not synchronize (#1198) (@withchao)
• 4b23171: fix: mogodb url connent (#1232) (@originnets)
• 2d86a1a: fix: remove repeat platform on online status. (#1221) (@FGadvancer)

Dependency updates

• 0363763: feat(deps): bump the gomod-deps group with 7 updates (#1248) (@dependabot[bot])

Other work

• 5e7e619: [Sweep Rules] Add unit test for RemoveRepeatedElementsInList function (#1224) (@sweep-ai[bot])
• c69d4da: fate: api, rpc QuitGroup req add userID (#1244) (@withchao)
• 363deff: feat(release-v3.4): Enhanced Build, Deployment, and Configuration Management for Optimized Performance and Automation (#1255) (@cubxxw)
• a648bee: optimize: reduce lock latency for conversation cache (#1231) (@rfyiamcool)

Full Changelog: v3.3.3-beta.2...v3.3.3-rc.0

Get Involved with OpenIM!

Your patronage towards OpenIM is greatly appreciated 🎉🎉.

If you encounter any problems during its usage, please create an issue in the GitHub repository, we're committed to resolving your problem as soon as possible.

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 Open-IM-Server 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 Open-IM-Server. 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! 🙌

v3.3.3-bate.4

Welcome to the v3.3.3-bate.4 release of OpenIM!🎉🎉!

We are excited to release v3.3.3-bate.4, Branch: https://github.com/openimsdk/open-im-server/tree/v3.3.3-bate.4 , Git hash [7e63800], Install Address: https://github.com/openimsdk/open-im-server/releases/tag/v3.3.3-bate.4

Learn more about versions of OpenIM:

• We release logs are recorded on ✨CHANGELOG

• For information on versions of OpenIM and how to maintain branches, read 📚this article

• If you wish to use mirroring, read OpenIM's 🤲image management policy

Want to be one of them 😘?

Note
@openimbot and @kubbot have made great contributions to the community as community 🤖robots(@openimsdk/bot), respectively.
Thanks to the @openimsdk/openim team for all their hard work on this release.
Thank you to all the 💕developers and contributors, people from all over the world, OpenIM brings us together
Contributions to this project are welcome! Please see CONTRIBUTING.md for details.

Changelog

New Features

• abf8e37: feat: Add the help chart script to support k8s deployment (#1145) (@xuexihuang)
• 8a54e46: feat: Add unit test for DeleteGroupMemberHash meth (#1200) (@sweep-ai[bot])
• 1c1f2a9: feat: Add unit test for RemoveRepeatedElementsInLi (#1223) (@sweep-ai[bot])
• b3d2f3b: feat:order logs by time desc (#1250) (@CNCSMonster)

Bug fixes

• 81cc1f3: fix: after modifying the avatar, offline users who joined the group did not synchronize (#1198) (@withchao)
• 2d86a1a: fix: remove repeat platform on online status. (#1221) (@FGadvancer)

Dependency updates

• 0363763: feat(deps): bump the gomod-deps group with 7 updates (#1248) (@dependabot[bot])

Other work

• 5e7e619: [Sweep Rules] Add unit test for RemoveRepeatedElementsInList function (#1224) (@sweep-ai[bot])
• df50971: docs: add openim docs (@cubxxw)
• 7e63800: docs: add openim images test (@cubxxw)
• a648bee: optimize: reduce lock latency for conversation cache (#1231) (@rfyiamcool)

Full Changelog: v3.3.3-beta.2...v3.3.3-bate.4

Get Involved with OpenIM!

Your patronage towards OpenIM is greatly appreciated 🎉🎉.

If you encounter any problems during its usage, please create an issue in the GitHub repository, we're committed to resolving your problem as soon as possible.

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 Open-IM-Server 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 Open-IM-Server. 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! 🙌

v3.3.3-beta.2

What's Changed

• Feature: add log support for developer by @FGadvancer in #1101
• feat: s3 public read by @withchao in #1080
• feat: send message add sendTime field for import messages. by @FGadvancer in #1104
• fix: turn on status notification that will burn after reading by @withchao in #1115
• fix: add callback for update user's info. by @FGadvancer in #1112
• 🧶 feat: Big job! kubernetes Deployment Design by @cubxxw in #1055
• fix: modifying user information notifications to join groups and group avatar issues by @withchao in #1147
• feat(deps): bump the gomod-deps group with 7 updates by @dependabot in #1150
• chore(deps): bump the github-actions group with 10 updates by @dependabot in #1142
• docs(main): update openim readme by @cubxxw in #1157
• fix: Implement Enhanced File Descriptor Limit Handling in Shell Script by @cubxxw in #1160
• feat: v2 to v3 data conversion by @withchao in #1164
• fix: make lint about cicd by @cubxxw in #1161
• docs: add openim docs by @cubxxw in #1165
• feat: v2 to v3 data conversion by @withchao in #1176
• Ensure Script Compatibility Across Different Bash Versions by @cubxxw in #1185
• feat: add redis cluster mode in option by @rfyiamcool in #1178
• optimize: reduce lock latency for localcache group by @rfyiamcool in #1179
• feat(deps): bump golang.org/x/net from 0.15.0 to 0.17.0 by @dependabot in #1188
• chore(deps): bump golang.org/x/net from 0.9.0 to 0.17.0 in /tools/url2im by @dependabot in #1189
• chore(deps): bump golang.org/x/net from 0.15.0 to 0.17.0 in /tools/data-conversion by @dependabot in #1187
• feat(deps): bump gorm.io/gorm from 1.25.4 to 1.25.5 by @dependabot in #1175
• feat(deps): bump github.com/tencentyun/cos-go-sdk-v5 from 0.7.43 to 0.7.44 by @dependabot in #1174
• Docs(main): Add English translation for README.md by @cubxxw in #1194
• bug:update a filed by @luhaoling in #1192
• fix: single chat unread status change. by @FGadvancer in #1171

New Contributors

• @rfyiamcool made their first contribution in #1178
• @luhaoling made their first contribution in #1192

Full Changelog: v3.3.3-beta.1...v3.3.3-beta.2

v3.3.3-beta.1

Welcome to the v3.3.3-beta.1 release of OpenIM!🎉🎉!

We are excited to release v3.3.3-beta.1, Branch: https://github.com/openimsdk/open-im-server/tree/v3.3.3-beta.1 , Git hash [1ed37f8], Install Address: https://github.com/openimsdk/open-im-server/releases/tag/v3.3.3-beta.1

Learn more about versions of OpenIM:

• We release logs are recorded on ✨CHANGELOG

• For information on versions of OpenIM and how to maintain branches, read 📚this article

• If you wish to use mirroring, read OpenIM's 🤲image management policy

Want to be one of them 😘?

Note
@openimbot and @kubbot have made great contributions to the community as community 🤖robots(@openimsdk/bot), respectively.
Thanks to the @openimsdk/openim team for all their hard work on this release.
Thank you to all the 💕developers and contributors, people from all over the world, OpenIM brings us together
Contributions to this project are welcome! Please see CONTRIBUTING.md for details.

Changelog

New Features

• 1ed37f8: feat: add openim task list (@cubxxw)

Full Changelog: v3.3.3-beta.0...v3.3.3-beta.1

Get Involved with OpenIM!

Your patronage towards OpenIM is greatly appreciated 🎉🎉.

If you encounter any problems during its usage, please create an issue in the GitHub repository, we're committed to resolving your problem as soon as possible.

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 Open-IM-Server 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 Open-IM-Server. 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! 🙌

v3.3.2

Welcome to the v3.3.2 release of OpenIM!🎉🎉!

We are excited to release v3.3.2, Branch: https://github.com/openimsdk/open-im-server/tree/v3.3.2 , Git hash [9673f50], Install Address: https://github.com/openimsdk/open-im-server/releases/tag/v3.3.2

Learn more about versions of OpenIM:

• We release logs are recorded on ✨CHANGELOG

• For information on versions of OpenIM and how to maintain branches, read 📚this article

• If you wish to use mirroring, read OpenIM's 🤲image management policy

Want to be one of them 😘?

Note
@openimbot and @kubbot have made great contributions to the community as community 🤖robots(@openimsdk/bot), respectively.
Thanks to the @openimsdk/openim team for all their hard work on this release.
Thank you to all the 💕developers and contributors, people from all over the world, OpenIM brings us together
Contributions to this project are welcome! Please see CONTRIBUTING.md for details.

Changelog

New Features

• 3e1b147: feat: choose whether to push group messages offline based on the user's session option settings (#1054) (@withchao)
• 5c31d12: feat: s3 public read (#1080) (@withchao)
• 9673f50: feat: send message add sendTime field for import messages. (#1104) (@FGadvancer)
• aa729a2: feat: set docs openim-server url address fix (#1043) (@cubxxw)
• 5fb9e94: feat: url to im s3 (#1067) (@withchao)

Bug fixes

• f393979: fix: openim logs release v3.3 (#1048) (@cubxxw)
• 72e5c4a: fix: set openim volume (#1051) (@cubxxw)

Other work

• bba662f: Feature: add log support for developer (#1101) (@FGadvancer)
• 40075de: fix update environment.sh (#1068) (@kubbot)
• 7a3c3d7: internal/msgtransfer: fix unreachable code issue (#1078) (@charles-chenzz)
• 2628874: 🎯 Optimize the deployment scheme to provide kubernetes deployment strategy (#1050) (@cubxxw)

Full Changelog: v3.3.0-rc.0...v3.3.2

Get Involved with OpenIM!

Your patronage towards OpenIM is greatly appreciated 🎉🎉.

If you encounter any problems during its usage, please create an issue in the GitHub repository, we're committed to resolving your problem as soon as possible.

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 Open-IM-Server 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 Open-IM-Server. 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! 🙌

v3.3.1

Welcome to the v3.3.1 release of OpenIM!🎉🎉!

We are excited to release v3.3.1, Branch: https://github.com/openimsdk/open-im-server/tree/v3.3.1 , Git hash [7aad1eb], Install Address: https://github.com/openimsdk/open-im-server/releases/tag/v3.3.1

Learn more about versions of OpenIM:

• We release logs are recorded on ✨CHANGELOG

• For information on versions of OpenIM and how to maintain branches, read 📚this article

• If you wish to use mirroring, read OpenIM's 🤲image management policy

Want to be one of them 😘?

Note
@openimbot and @kubbot have made great contributions to the community as community 🤖robots(@openimsdk/bot), respectively.
Thanks to the @openimsdk/openim team for all their hard work on this release.
Thank you to all the 💕developers and contributors, people from all over the world, OpenIM brings us together
Contributions to this project are welcome! Please see CONTRIBUTING.md for details.

Changelog

New Features

• 82f741c: feat: add openim test: (@cubxxw)
• e334bfd: feat: add openim test: (@cubxxw)

Bug fixes

• 7aad1eb: fix: fix env api url (@cubxxw)

Full Changelog: v3.3.1-beta.0...v3.3.1

Get Involved with OpenIM!

Your patronage towards OpenIM is greatly appreciated 🎉🎉.

If you encounter any problems during its usage, please create an issue in the GitHub repository, we're committed to resolving your problem as soon as possible.

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 Open-IM-Server 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 Open-IM-Server. 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! 🙌

v3.3.1-beta.0

Welcome to the v3.3.1-beta.0 release of OpenIM!🎉🎉!

We are excited to release v3.3.1-beta.0, Branch: https://github.com/openimsdk/open-im-server/tree/v3.3.1-beta.0 , Git hash [73733ca], Install Address: https://github.com/openimsdk/open-im-server/releases/tag/v3.3.1-beta.0

Learn more about versions of OpenIM:

• We release logs are recorded on ✨CHANGELOG

• For information on versions of OpenIM and how to maintain branches, read 📚this article

• If you wish to use mirroring, read OpenIM's 🤲image management policy

Want to be one of them 😘?

Note
@openimbot and @kubbot have made great contributions to the community as community 🤖robots(@openimsdk/bot), respectively.
Thanks to the @openimsdk/openim team for all their hard work on this release.
Thank you to all the 💕developers and contributors, people from all over the world, OpenIM brings us together
Contributions to this project are welcome! Please see CONTRIBUTING.md for details.

Changelog

New Features

• 56144ed: feat: add openim server test about openim web (@cubxxw)
• ad8b5b4: feat: add openim server test about openim web (@cubxxw)
• 73733ca: feat: add openim server test about openim web (@cubxxw)
• 4ecb2f8: feat: add options about helm deploy (@cubxxw)
• aa729a2: feat: set docs openim-server url address fix (#1043) (@cubxxw)

Bug fixes

• 10a0bd0: fix: fix docker compose file (@cubxxw)
• f393979: fix: openim logs release v3.3 (#1048) (@cubxxw)
• 72e5c4a: fix: set openim volume (#1051) (@cubxxw)

Other work

• 2628874: 🎯 Optimize the deployment scheme to provide kubernetes deployment strategy (#1050) (@cubxxw)

Full Changelog: v3.3.0-rc.0...v3.3.1-beta.0

Get Involved with OpenIM!

Your patronage towards OpenIM is greatly appreciated 🎉🎉.

If you encounter any problems during its usage, please create an issue in the GitHub repository, we're committed to resolving your problem as soon as possible.

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 Open-IM-Server 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 Open-IM-Server. 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! 🙌

v3.3.0-rc.1

Welcome to the v3.3.0-rc.1 release of OpenIM!🎉🎉!

We are excited to release v3.3.0-rc.1, Branch: https://github.com/openimsdk/open-im-server/tree/v3.3.0-rc.1 , Git hash [56144ed], Install Address: https://github.com/openimsdk/open-im-server/releases/tag/v3.3.0-rc.1

Learn more about versions of OpenIM:

• We release logs are recorded on ✨CHANGELOG

• For information on versions of OpenIM and how to maintain branches, read 📚this article

• If you wish to use mirroring, read OpenIM's 🤲image management policy

Want to be one of them 😘?

Note
@openimbot and @kubbot have made great contributions to the community as community 🤖robots(@openimsdk/bot), respectively.
Thanks to the @openimsdk/openim team for all their hard work on this release.
Thank you to all the 💕developers and contributors, people from all over the world, OpenIM brings us together
Contributions to this project are welcome! Please see CONTRIBUTING.md for details.

Changelog

New Features

• 56144ed: feat: add openim server test about openim web (@cubxxw)
• 4ecb2f8: feat: add options about helm deploy (@cubxxw)
• aa729a2: feat: set docs openim-server url address fix (#1043) (@cubxxw)

Bug fixes

• 10a0bd0: fix: fix docker compose file (@cubxxw)
• f393979: fix: openim logs release v3.3 (#1048) (@cubxxw)
• 72e5c4a: fix: set openim volume (#1051) (@cubxxw)

Other work

• 2628874: 🎯 Optimize the deployment scheme to provide kubernetes deployment strategy (#1050) (@cubxxw)

Full Changelog: v3.3.0-rc.0...v3.3.0-rc.1

Get Involved with OpenIM!

Your patronage towards OpenIM is greatly appreciated 🎉🎉.

If you encounter any problems during its usage, please create an issue in the GitHub repository, we're committed to resolving your problem as soon as possible.

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 Open-IM-Server 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 Open-IM-Server. 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! 🙌

v3.3.0

Welcome to the v3.3.0 release of OpenIM!🎉🎉!

We are excited to release v3.3.0, Branch: https://github.com/openimsdk/open-im-server/tree/v3.3.0 , Git hash [aa729a2], Install Address: https://github.com/openimsdk/open-im-server/releases/tag/v3.3.0

Learn more about versions of OpenIM:

• We release logs are recorded on ✨CHANGELOG

• For information on versions of OpenIM and how to maintain branches, read 📚this article

• If you wish to use mirroring, read OpenIM's 🤲image management policy

Want to be one of them 😘?

Note
@openimbot and @kubbot have made great contributions to the community as community 🤖robots(@openimsdk/bot), respectively.
Thanks to the @openimsdk/openim team for all their hard work on this release.
Thank you to all the 💕developers and contributors, people from all over the world, OpenIM brings us together
Contributions to this project are welcome! Please see CONTRIBUTING.md for details.

Changelog

New Features

• aa729a2: feat: set docs openim-server url address fix (#1043) (@cubxxw)

Full Changelog: v3.3.0-rc.0...v3.3.0

Get Involved with OpenIM!

Your patronage towards OpenIM is greatly appreciated 🎉🎉.

If you encounter any problems during its usage, please create an issue in the GitHub repository, we're committed to resolving your problem as soon as possible.

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 Open-IM-Server 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 Open-IM-Server. 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! 🙌

v3.3.0-rc.0

Welcome to the v3.3.0-rc.0 release of OpenIM!🎉🎉!

We are excited to release v3.3.0-rc.0, Branch: https://github.com/openimsdk/open-im-server/tree/v3.3.0-rc.0 , Git hash [186952a], Install Address: https://github.com/openimsdk/open-im-server/releases/tag/v3.3.0-rc.0

Learn more about versions of OpenIM:

• We release logs are recorded on ✨CHANGELOG

• For information on versions of OpenIM and how to maintain branches, read 📚this article

• If you wish to use mirroring, read OpenIM's 🤲image management policy

Want to be one of them 😘?

Note
@openimbot and @kubbot have made great contributions to the community as community 🤖robots(@openimsdk/bot), respectively.
Thanks to the @openimsdk/openim team for all their hard work on this release.
Thank you to all the 💕developers and contributors, people from all over the world, OpenIM brings us together
Contributions to this project are welcome! Please see CONTRIBUTING.md for details.

Changelog

New Features

• 497302c: feat: Automating openim-docker synchronization (#962) (@cubxxw)
• 35e48b6: feat: remove redundant readline (#1027) (@charlie-bit)
• 2cca15d: feat: update demo scripts (#1016) (@cubxxw)
• 87766af: 🔥Super feat: OpenIM CTL optimization is supported (#926) (@cubxxw)

Bug fixes

• 96e09a1: fix: Transfer Group Questions (#977) (@withchao)
• da89121: fix: add openim server deploy (#1036) (@cubxxw)
• 781b13c: fix: default friends and groups, no new sessions triggered (#960) (@withchao)
• db9dbd4: fix: jpush return a nil pointer panic (#1005) (@withchao)
• f2977b6: fix: limit group chat has read message. (@FGadvancer)
• 94a4199: fix: push redis pkg (#1019) (@withchao)
• 4ce4548: fix: repeated modification session notification (#991) (@withchao)
• 4a0e949: fix: repeated modification session notification (#994) (@withchao)
• eae79d5: fix: user offline push (#1015) (@withchao)
• d753234: fix:sent message already has a timestamp, no timestamp will be generated (#982) (@plutoyty)

Dependency updates

• 1e592f3: feat(deps): bump the gomod-deps group with 9 updates (#1003) (@dependabot[bot])

Other work

• 3ecce40: Create sync-release.yml (#963) (@cubxxw)
• cc29fc8: Create sync-release.yml (#964) (@cubxxw)
• 786090f: Group members do not set their names and avatars to be updated in real time (#974) (@withchao)
• e50c903: Update go.work (#1012) (@cubxxw)
• f4e4bfd: Update msg.go (#958) (@g6619563)
• 5b478e3: Update sync-release.yml (#965) (@cubxxw)
• 9d6b153: add GetSpecifiedFriendsInfo (#986) (@withchao)
• de50331: docs: fix go_mode.md (#1031) (@CNCSMonster)
• 721af24: docs: update openim readme (#1017) (@cubxxw)
• 186952a: refactor: change project module name. (#1038) (@FGadvancer)
• 687614d: refactor:Optimization of text messages when accepting message req (#981) (@plutoyty)
• 6fc15d4: refactor:Returns [] an empty array when no platform is online, instead of null (#970) (@plutoyty)
• 85bd38d: remove pprop (#988) (@withchao)

Full Changelog: v3.2.2-alpha.0...v3.3.0-rc.0

Get Involved with OpenIM!

Your patronage towards OpenIM is greatly appreciated 🎉🎉.

If you encounter any problems during its usage, please create an issue in the GitHub repository, we're committed to resolving your problem as soon as possible.

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 Open-IM-Server 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 Open-IM-Server. 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! 🙌