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 [186952ab4], 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

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

Bug fixes

• 96e09a1b370e446f37b25a6babe1c542ee6f4423: fix: Transfer Group Questions (#977) (@withchao)
• da8912121fa6c34c6bc6e89f62c27af0be7fc786: fix: add openim server deploy (#1036) (@cubxxw)
• 781b13c604e97a8951b7d38c0d41438c3f982208: fix: default friends and groups, no new sessions triggered (#960) (@withchao)
• db9dbd4385e723a256fce11fe1b2d791580069c7: fix: jpush return a nil pointer panic (#1005) (@withchao)
• f2977b6837ec671203388aee44baf9edcbf2c02e: fix: limit group chat has read message. (@FGadvancer)
• 94a41998552aa69b40a736f798c380a0c3074784: fix: push redis pkg (#1019) (@withchao)
• 4ce4548ca1afe11c42507d732ffeb5f6324e6afc: fix: repeated modification session notification (#991) (@withchao)
• 4a0e949569daa662591a1e6400953ce61affd45e: fix: repeated modification session notification (#994) (@withchao)
• eae79d567cad1e31d84b64b3ece29487a4d8eca3: fix: user offline push (#1015) (@withchao)
• d7532347ad30d03158caf51d0f72607e290c86dc: fix:sent message already has a timestamp, no timestamp will be generated (#982) (@plutoyty)

Dependency updates

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

Other work

• 3ecce40b87e99109bcb3e2bccd5dcbab545a45dd: Create sync-release.yml (#963) (@cubxxw)
• cc29fc85d8e309159c8c03cfd7b129ac9964c700: Create sync-release.yml (#964) (@cubxxw)
• 786090f74237dd0e6a2b1e0d4a26af2a3e6111c7: Group members do not set their names and avatars to be updated in real time (#974) (@withchao)
• e50c903ecb5ceaa506d75da1ad72d6360f04c13c: Update go.work (#1012) (@cubxxw)
• f4e4bfd6399d3478ec244f81f10dbeef1797c5bd: Update msg.go (#958) (@g6619563)
• 5b478e3d632230aa30f6c6a41a80a7a8bbf13f6d: Update sync-release.yml (#965) (@cubxxw)
• 9d6b1536d26401f2d685a73d2b46a1fcb347b075: add GetSpecifiedFriendsInfo (#986) (@withchao)
• de50331d7a72b8ce6dfcfd7c641aa4f4e982766b: docs: fix go_mode.md (#1031) (@CNCSMonster)
• 721af24df67abf0908bc4790cc6dda526b625f20: docs: update openim readme (#1017) (@cubxxw)
• 186952ab46f44ede509b1a8104a248efbf824654: refactor: change project module name. (#1038) (@FGadvancer)
• 687614d3f432ab5629b97b35d37f76e25349a898: refactor:Optimization of text messages when accepting message req (#981) (@plutoyty)
• 6fc15d4f7af5f1cb01dcc35afda2179eec66a859: refactor:Returns [] an empty array when no platform is online, instead of null (#970) (@plutoyty)
• 85bd38d6d4af0d05460a5e54c289e4f6db5752ef: remove pprop (#988) (@withchao)

Full Changelog: https://github.com/openimsdk/open-im-server/compare/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! 🙌