Bump up yorkie-js-sdk to 0.5.0

[devleejb]

What this PR does / why we need it:

Bump up yorkie-js-sdk to `0.5.0``

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Additional documentation:

Checklist:

• Added relevant tests or not required
• Didn't break anything

Summary by CodeRabbit

• New Features
  • Upgraded the Yorkie service and SDK to version 0.5.0, potentially introducing new features, bug fixes, and performance improvements.
• Bug Fixes
  • Enhanced functionality and reliability with the updated Yorkie service and SDK version.

[coderabbitai]

Walkthrough

The changes involve updating the version of the Yorkie service and its JavaScript SDK across multiple configuration files. The Docker Compose files for both the backend services reflect a version upgrade from 0.4.31 to 0.5.0, while the frontend's package.json also shows the same SDK version change. These updates may introduce new features, bug fixes, or performance improvements.

Changes

Files	Change Summary
backend/docker/docker-compose-full.yml, backend/docker/docker-compose.yml	Updated Yorkie service image version from 0.4.31 to 0.5.0.
frontend/package.json	Updated yorkie-js-sdk dependency version from 0.4.31 to 0.5.0.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant Frontend
    participant Backend
    participant YorkieService

    Client->>Frontend: Request data
    Frontend->>Backend: Fetch data
    Backend->>YorkieService: Get data
    YorkieService-->>Backend: Return data
    Backend-->>Frontend: Send data
    Frontend-->>Client: Display data

Loading

🐇 "Oh, hop and cheer, the updates are here,
With Yorkie's new version, let’s spread the good cheer!
Bugs are now fixed, and features anew,
Jumping for joy, we’ll code right on through!
So gather your carrots, let’s code with delight,
For Yorkie’s fresh magic makes everything bright!" 🥕✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between ba3d54d and de8f72b.

Files ignored due to path filters (1)

• frontend/package-lock.json is excluded by !**/package-lock.json

Files selected for processing (3)

• backend/docker/docker-compose-full.yml (1 hunks)
• backend/docker/docker-compose.yml (1 hunks)
• frontend/package.json (1 hunks)

Additional comments not posted (3)

backend/docker/docker-compose.yml (1)

5-5: Version update approved.

The update from yorkieteam/yorkie:0.4.31 to yorkieteam/yorkie:0.5.0 is noted. It's crucial to ensure that this version bump integrates smoothly with the existing configurations and does not introduce any breaking changes.

Please verify the compatibility of the new version with the existing system configurations and ensure that all functionalities are working as expected.

backend/docker/docker-compose-full.yml (1)

37-37: Approve the version update for the Yorkie service.

The update from yorkieteam/yorkie:0.4.31 to yorkieteam/yorkie:0.5.0 is noted. It's crucial to ensure that this version is compatible with the existing system configurations and dependent services.

Run the following script to verify the compatibility of the new version with the existing system:

frontend/package.json (1)

78-78: Approved: SDK version update.

The update of yorkie-js-sdk from 0.4.31 to 0.5.0 is noted. Ensure that this version update has been tested thoroughly, especially for any breaking changes or new features that might affect the existing functionality.