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.

OpenIM-v3.0

OpenIM Server 3.0 Release

Announcement: OpenIM v3.0.0 Release is Here! We are thrilled to present the long-awaited release version of OpenIM v3.0.0! This update brings several exciting enhancements and improvements that will elevate your messaging experience. Let's dive into the key features:

• Improved Message Propagation: With the introduction of the read diffusion model, network load is reduced as messages are only sent to users who actually need to receive them. This eliminates the need for broadcasting to all users, especially benefiting group chats. No more duplicate messages flooding your conversations!

• Streamlined RPC and API Code : By leveraging reflection and generics, we have simplified the RPC and API code, eliminating redundancy and making the codebase more flexible and maintainable. This optimization boosts development efficiency and minimizes the possibility of errors.

• Standardized Error Codes: We have implemented a unified set of error codes, making problem identification and troubleshooting processes a breeze. Now, potential issues can be quickly located and resolved, ensuring enhanced application stability and reliability.

• Integrated ZooKeeper with gRPC: Managing and maintaining services is now more convenient than ever. By integrating ZooKeeper as a service registry center, you can effortlessly add, remove, and monitor service states, ensuring system availability and resilience.

• Optimized WebSocket Long Connection Management: Our server now offers enhanced performance and stability by efficiently managing long-lasting connections. This optimization reduces server resource consumption, resulting in an improved user experience.

• Server-Side Session Model: Say goodbye to unsynchronized unread messages in sessions! With the implementation of a server-side session model, the state of each session is diligently tracked and managed. This ensures that users receive the latest messages across multiple devices, preventing information loss or duplication.

• On-Demand Message Loading: We have tackled the latency issue when logging in with a new device. Now, messages are dynamically loaded to avoid overwhelming data retrieval during login. This enhancement greatly improves user experience and system responsiveness.

Explore the release in detail(https://github.com/OpenIMSDK/Open-IM-Server/releases/tag/v3.0.0). We're excited to bring you these fantastic updates, and look forward to your valuable feedback as we continue to refine OpenIM Server.

What's Changed

• fix: rpc mw mismatch key by @withchao in #546
• fix bug: log path and user rpc by @wangchuxiao-dev in #547
• fix: scripts and release by @cubxxw in #552
• new feature: add batch send msg by @wangchuxiao-dev in #560
• feat: Add light mode and dark mode.(#89) by @cubxxw in #558
• fix get groups bug by @hanzhixiao in #562
• feat: Add light mode and dark mode.(#89) by @cubxxw in #564
• fix bug #545 by @plutoyty in #555
• message for your changes by @hanzhixiao in #565
• debug by @hanzhixiao in #566
• fix bug: multiple gateway kick user by @wangchuxiao-dev in #568
• fix: implement of GetUsersOnlineStatus (#567) by @BanTanger in #569

Full Changelog: v3.0.0-alpha.1...v3.0.0

Release Branch：https://github.com/OpenIMSDK/Open-IM-Server/tree/release-v3.0

git clone https://github.com/OpenIMSDK/Open-IM-Server openim
cd openim
git checkout release-v3.0
# edit config/config.yaml
chmod +x ./install_im_server.sh
./install_im_server.sh

OpenIM-v3.0.0-rc.2

Announcement: OpenIM v3.0.0 Pre-Release is Here! We are thrilled to present the long-awaited pre-release version of OpenIM v3.0.0! This update brings several exciting enhancements and improvements that will elevate your messaging experience. Let's dive into the key features:

• Improved Message Propagation: With the introduction of the read diffusion model, network load is reduced as messages are only sent to users who actually need to receive them. This eliminates the need for broadcasting to all users, especially benefiting group chats. No more duplicate messages flooding your conversations!

• Streamlined RPC and API Code : By leveraging reflection and generics, we have simplified the RPC and API code, eliminating redundancy and making the codebase more flexible and maintainable. This optimization boosts development efficiency and minimizes the possibility of errors.

• Standardized Error Codes: We have implemented a unified set of error codes, making problem identification and troubleshooting processes a breeze. Now, potential issues can be quickly located and resolved, ensuring enhanced application stability and reliability.

• Integrated ZooKeeper with gRPC: Managing and maintaining services is now more convenient than ever. By integrating ZooKeeper as a service registry center, you can effortlessly add, remove, and monitor service states, ensuring system availability and resilience.

• Optimized WebSocket Long Connection Management: Our server now offers enhanced performance and stability by efficiently managing long-lasting connections. This optimization reduces server resource consumption, resulting in an improved user experience.

• Server-Side Session Model: Say goodbye to unsynchronized unread messages in sessions! With the implementation of a server-side session model, the state of each session is diligently tracked and managed. This ensures that users receive the latest messages across multiple devices, preventing information loss or duplication.

• On-Demand Message Loading: We have tackled the latency issue when logging in with a new device. Now, messages are dynamically loaded to avoid overwhelming data retrieval during login. This enhancement greatly improves user experience and system responsiveness.

Explore the release in detail(https://github.com/OpenIMSDK/Open-IM-Server/releases/tag/v3.0.0-alpha.0). We're excited to bring you these fantastic updates, and look forward to your valuable feedback as we continue to refine OpenIM Server.

Release Branch：https://github.com/OpenIMSDK/Open-IM-Server/tree/release-v3.0.0-rc.2

What's Changed

• fix: rpc mw mismatch key by @withchao in #546
• fix bug: log path and user rpc by @wangchuxiao-dev in #547

Full Changelog: v3.0.0-alpha.1...v3.0.0-rc.2

OpenIM-v3.0.0-alpha.1

OpenIM v3.0.0 Release

Announcement: OpenIM v3.0.0 Pre-Release is Here! We are thrilled to present the long-awaited pre-release version of OpenIM v3.0.0! This update brings several exciting enhancements and improvements that will elevate your messaging experience. Let's dive into the key features:

• Improved Message Propagation: With the introduction of the read diffusion model, network load is reduced as messages are only sent to users who actually need to receive them. This eliminates the need for broadcasting to all users, especially benefiting group chats. No more duplicate messages flooding your conversations!

• ****Streamlined RPC and API Code: By leveraging reflection and generics, we have simplified the RPC and API code, eliminating redundancy and making the codebase more flexible and maintainable. This optimization boosts development efficiency and minimizes the possibility of errors.

• Standardized Error Codes: We have implemented a unified set of error codes, making problem identification and troubleshooting processes a breeze. Now, potential issues can be quickly located and resolved, ensuring enhanced application stability and reliability.

• Integrated ZooKeeper with gRPC: Managing and maintaining services is now more convenient than ever. By integrating ZooKeeper as a service registry center, you can effortlessly add, remove, and monitor service states, ensuring system availability and resilience.

• Optimized WebSocket Long Connection Management: Our server now offers enhanced performance and stability by efficiently managing long-lasting connections. This optimization reduces server resource consumption, resulting in an improved user experience.

• Server-Side Session Model: Say goodbye to unsynchronized unread messages in sessions! With the implementation of a server-side session model, the state of each session is diligently tracked and managed. This ensures that users receive the latest messages across multiple devices, preventing information loss or duplication.

• On-Demand Message Loading: We have tackled the latency issue when logging in with a new device. Now, messages are dynamically loaded to avoid overwhelming data retrieval during login. This enhancement greatly improves user experience and system responsiveness.

Explore the [release in detail](https://github.com/OpenIMSDK/Open-IM-Server/releases/tag/v3.0.0-alpha.0). We're excited to bring you these fantastic updates, and look forward to your valuable feedback as we continue to refine OpenIM Server.

Release Branch：https://github.com/OpenIMSDK/Open-IM-Server/releases/tag/v3.0.0-alpha.1

What's Changed

• feat: add scripts by @cubxxw in #514
• feat: add scripts by @cubxxw in #515
• cicd: update openim-ci.yml by @plutoyty in #528
• feat: add scripts by @cubxxw in #525
• add MongoDB,Redis,Kafka retry mechanism by @plutoyty in #518
• all back-office api by @hanzhixiao in #533
• fix: get user online status #472 by @FGadvancer in #527
• fix bug: friend, args error by @wangchuxiao-dev in #534
• fix: conflict resolve main by @FGadvancer in #537
• fix: minio auto make bucket by @withchao in #538
• url to uri by @plutoyty in #539
• feat: add test file by @cubxxw in #540
• Fix/v3 error by @hanzhixiao in #542
• fix conflict by @hanzhixiao in #543

New Contributors

• @withchao made their first contribution in #538

Full Changelog: v3.0.0-alpha.0...v3.0.0-alpha.1

OpenIM-v3.0.0-alpha.0

Version logging for OpenIM

• when we change the message propagation model from write diffusion to read diffusion, it can bring some advantages. First, the read diffusion model can reduce network load because messages only need to be sent to users who actually need to receive them, rather than broadcasting to all users. This is especially important for group chats as it avoids sending a large number of duplicate messages. 😊

• By using reflection and generics to simplify RPC and API code, we can reduce redundant template code and make the code more flexible and maintainable. This simplification can also improve development efficiency and reduce the possibility of errors. 😄

• Standardizing error codes can greatly simplify problem identification and troubleshooting processes. By defining a unified set of error codes, we can quickly locate and resolve potential issues, improving application stability and reliability. 😉

• Integrating ZooKeeper with gRPC enables service registration and discovery, making service management and maintenance more convenient. By using ZooKeeper as a service registry center, we can easily add, remove, and monitor service states to ensure system availability and resilience. 😃

• Optimizing WebSocket long connection management can enhance system performance and stability. By effectively managing long-lasting connections, we can reduce server resource consumption and provide a better user experience. 😊

• Introducing a server-side session model can solve the problem of unsynchronized unread messages in sessions. By tracking and managing the state of each session, we can ensure that users can receive the latest messages when using the application on different devices, avoiding information loss or duplication. 😄

• Implementing on-demand message loading can solve the latency issue when logging in with a new device. By dynamically loading messages, we can avoid loading a large amount of data at once, which can slow down the login process, thus improving user experience and system responsiveness. 😊

Test branch

release-v3.0.0-alpha.0: https://github.com/OpenIMSDK/Open-IM-Server/tree/release-v3.0.0-alpha.0

CHAGELOG

What's Changed

• feat: adding actions by @cubxxw in #461
• V3dev by @wangchuxiao-dev in #463
• Feat/parameter check by @hanzhixiao in #465
• Docker compose bug by @YuanJey in #471
• feat: adding actions by @cubxxw in #462
• feat: add the changelog by @cubxxw in #490
• fix: docker file path by @cubxxw in #492
• fix: docker file path by @cubxxw in #495
• Add database retry by @plutoyty in #493
• feat: add logic to deploy images by @cubxxw in #497
• chore: use fmt.Errorf(...) instead of errors.New(fmt.Sprintf(...)) by @testwill in #469
• For "add database retry" add test by @plutoyty in #500
• merge v3dev into main by @FGadvancer in #504
• fix: fix start scripts by @cubxxw in #501
• Delete .idea directory by @cubxxw in #507
• fix: remove some structs by @FGadvancer in #509
• fix: remove import C by @FGadvancer in #511
• fix: add msg transfer file by @FGadvancer in #512

New Contributors

• @plutoyty made their first contribution in #493
• @testwill made their first contribution in #469
• @FGadvancer made their first contribution in #504

Full Changelog: https://github.com/OpenIMSDK/Open-IM-Server/commits/v3.0.0-alpha.0

Unreleased

• Version logging for OpenIM
  • Unreleased
  • v2.9.0 - 2023-07-04
    • Reverts
    • Pull Requests
  • v2.3.3 - 2022-09-18
  • v2.3.2 - 2022-09-09
  • v2.3.0-rc2 - 2022-07-29
  • v2.3.0-rc1 - 2022-07-25
  • v2.3.0-rc0 - 2022-07-15
  • v2.2.0 - 2022-07-01
  • v2.1.0 - 2022-06-17
    • Pull Requests
  • v2.0.10 - 2022-05-13
  • v2.0.9 - 2022-04-29
    • Reverts
    • Pull Requests
  • v2.0.7 - 2022-04-08
    • Pull Requests
  • v2.0.6 - 2022-04-01
    • Pull Requests
  • v2.0.5 - 2022-03-24
  • v2.04 - 2022-03-18
  • v2.0.3 - 2022-03-11
  • v2.0.2 - 2022-03-04
    • Pull Requests
  • v2.0.1 - 2022-02-25
  • v2.0.0 - 2022-02-23
  • v1.0.7 - 2021-12-17
  • v1.0.6 - 2021-12-10
  • v1.0.5 - 2021-12-03
  • v1.0.4 - 2021-11-25
  • v1.0.3 - 2021-11-12
  • v1.0.1 - 2021-11-04
  • v1.0.0 - 2021-10-28
    • Reverts

v2.9.0 - 2023-07-04

Reverts

• update etcd to v3.5.2 (#206)

Pull Requests

• Merge branch 'tuoyun'

v2.3.3 - 2022-09-18

v2.3.2 - 2022-09-09

v2.3.0-rc2 - 2022-07-29

v2.3.0-rc1 - 2022-07-25

v2.3.0-rc0 - 2022-07-15

v2.2.0 - 2022-07-01

v2.1.0 - 2022-06-17

Pull Requests

• Merge branch 'tuoyun'
• Merge branch 'tuoyun'
• Merge branch 'tuoyun'

v2.0.10 - 2022-05-13

v2.0.9 - 2022-04-29

Reverts

• update etcd to v3.5.2 (#206)

Pull Requests

v2.0.7 - 2022-04-08

Pull Requests

• Merge branch 'tuoyun'

v2.0.6 - 2022-04-01

Pull Requests

• Merge branch 'tuoyun'

v2.0.5 - 2022-03-24

v2.04 - 2022-03-18

v2.0.3 - 2022-03-11

v2.0.2 - 2022-03-04

Pull Requests

• Merge branch 'tuoyun'
• Merge branch 'tuoyun'
• Merge branch 'tuoyun'
• Merge branch 'tuoyun'

v2.0.1 - 2022-02-25

v2.0.0 - 2022-02-23

v1.0.7 - 2021-12-17

v1.0.6 - 2021-12-10

v1.0.5 - 2021-12-03

v1.0.4 - 2021-11-25

v1.0.3 - 2021-11-12

[v1.0.1] - 2021-11-04

v1.0.0 - 2021-10-28

Reverts

• friend modify
• update

[...