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! 🙌

v3.3.0-beta.4

Welcome to the v3.3.0-beta.4 release of OpenIM!🎉🎉!

We are excited to release v3.3.0-beta.4, Branch: https://github.com/OpenIMSDK/Open-IM-Server/tree/v3.3.0-beta.4 , Git hash [d187f53], Install Address: https://github.com/OpenIMSDK/Open-IM-Server/releases/tag/v3.3.0-beta.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

• 77733fd: feat: docker compose (@cubxxw)
• 108c4b1: feat: set config file path (@cubxxw)
• fa263b9: feat: set config file path (@cubxxw)
• 3c796b7: feat: set config file path (@cubxxw)

Bug fixes

• 103aa98: fix: kafka environment port (@cubxxw)
• 347f6f3: fix: kafka environment port (@cubxxw)
• 5134fdf: fix: kafka environment port (@cubxxw)
• d187f53: fix: kafka environment port (@cubxxw)
• 475ad26: fix: scripts fix (@cubxxw)
• ca72ce2: fix: scripts fix (@cubxxw)
• e4eb8ff: fix: scripts fix (@cubxxw)

Full Changelog: v3.3.0-beta.3...v3.3.0-beta.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.2.2

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

We are excited to release v3.2.2, Branch: https://github.com/OpenIMSDK/Open-IM-Server/tree/v3.2.2 , Git hash [d687d26], Install Address: https://github.com/OpenIMSDK/Open-IM-Server/releases/tag/v3.2.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

• 497302c: feat: Automating openim-docker synchronization (#962) (@cubxxw)
• 3fdc510: feat: add docker buildx images is openim-web (@cubxxw)
• 9eee94e: feat: add docker buildx images is openim-web (@cubxxw)
• 59c6635: feat: add more test (@cubxxw)
• 489e4fc: feat: add more test (@cubxxw)
• b37aa92: feat: add more test (@cubxxw)
• 2f7f45a: feat: add more test (@cubxxw)
• cb31569: feat: add more test (@cubxxw)
• 17bc959: feat: add more test (@cubxxw)
• 607d97f: feat: add more test code (@cubxxw)
• 2c44498: feat: add more test code (@cubxxw)
• cb707f0: feat: add more test code (@cubxxw)
• b465caa: feat: add more test project (@cubxxw)
• b85750d: feat: add more test project (@cubxxw)
• 7ec5d76: feat: add more test project (@cubxxw)
• 5f59019: feat: add more test project (@cubxxw)
• 270e14d: feat: add test file (@cubxxw)
• 3f2d771: feat: add test file (@cubxxw)
• 5379603: feat: add versionchecker deploy (@cubxxw)
• 0d59d42: feat: docker compose (@cubxxw)
• 8a226a7: feat: fix go work go version and build scripts (@cubxxw)
• 95091e7: feat: init project (@cubxxw)
• a02e0c3: feat: init project (@cubxxw)
• 6db9e2c: feat: sava images file (@cubxxw)
• 0dd3d96: feat: set config file path (@cubxxw)
• 8024985: feat: set config file path (@cubxxw)
• 9200de7: feat: set config file path (@cubxxw)
• 83917d1: feat: set more help and port set (@cubxxw)
• 906fb72: feat: set more help and port set (@cubxxw)
• 7f90eb5: feat: update openim-web (@cubxxw)
• 80c985a: feat: update openim-web (@cubxxw)
• 46c26b8: feat: update openim-web (@cubxxw)

Bug fixes

• 96e09a1: fix: Transfer Group Questions (#977) (@withchao)
• 781b13c: fix: default friends and groups, no new sessions triggered (#960) (@withchao)
• 43bdd41: fix: fix actions no pass (@cubxxw)
• 8f17321: fix: fix chat bug (@cubxxw)
• f19c9d8: fix: kafka environment port (@cubxxw)
• b2bb86d: fix: kafka environment port (@cubxxw)
• 15a09c9: fix: kafka environment port (@cubxxw)
• d687d26: fix: kafka environment port (@cubxxw)
• f2977b6: fix: limit group chat has read message. (@FGadvancer)
• 4ce4548: fix: repeated modification session notification (#991) (@withchao)
• 4a0e949: fix: repeated modification session notification (#994) (@withchao)
• ef0ce13: fix: scripts fix (@cubxxw)
• bf67a56: fix: scripts fix (@cubxxw)
• 9c4517a: fix: scripts fix (@cubxxw)
• 7b07257: fix: update slack link (@cubxxw)
• fda2958: fix: update slack link (@cubxxw)
• d753234: fix:sent message already has a timestamp, no timestamp will be generated (#982) (@plutoyty)

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)
• f4e4bfd: Update msg.go (#958) (@g6619563)
• 5b478e3: Update sync-release.yml (#965) (@cubxxw)
• 9d6b153: add GetSpecifiedFriendsInfo (#986) (@withchao)
• 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.2.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.0-beta.3

Welcome to the v3.3.0-beta.3 release of OpenIM!🎉🎉!

We are excited to release v3.3.0-beta.3, Branch: https://github.com/OpenIMSDK/Open-IM-Server/tree/v3.3.0-beta.3 , Git hash [cffefbd], Install Address: https://github.com/OpenIMSDK/Open-IM-Server/releases/tag/v3.3.0-beta.3

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

• cffefbd: feat: add more test (@cubxxw)

Full Changelog: v3.3.0-beta.2...v3.3.0-beta.3

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! 🙌