Bump up Yorkie to v0.5.1

[chacha912]

What this PR does / why we need it?

Bump up Yorkie to v0.5.1

Any background context you want to provide?

What are the relevant tickets?

Fixes #

Checklist

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

Summary by CodeRabbit

• New Features
  • Updated project version to 0.5.1, enhancing overall performance and stability.
  • Updated the yorkie-js-sdk dependency to version 0.5.1 for improved functionality.

[coderabbitai]

Walkthrough

The changes in this pull request involve updates to the versioning of the project and its dependencies. The environment variable VITE_JS_SDK_VERSION has been incremented from 0.5.0 to 0.5.1 in the .env file. Additionally, the package.json file reflects the project's version change from 0.5.0 to 0.5.1, along with a corresponding update to the yorkie-js-sdk dependency version from ^0.5.0 to ^0.5.1.

Changes

File	Change Summary
.env	Updated VITE_JS_SDK_VERSION from 0.5.0 to 0.5.1
package.json	Updated project version from 0.5.0 to 0.5.1 and yorkie-js-sdk version from ^0.5.0 to ^0.5.1

Poem

In the garden where code does bloom,
Versions rise, dispelling gloom.
From 0.5.0 to 0.5.1,
A hop, a skip, the change is done!
Dependencies fresh, like morning dew,
A brighter path for all to pursue! 🐇✨

---

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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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

🧹 Outside diff range and nitpick comments (1)

package.json (1)

Line range hint 1-145: Summary: Changes are minimal and focused. Ensure thorough testing.

The changes in this file are limited to updating the project version and the "yorkie-js-sdk" dependency, which aligns perfectly with the PR objectives. No other unexpected modifications were found.

To ensure the update doesn't introduce any regressions:

1. Perform a comprehensive test of all features that depend on the Yorkie SDK.
2. Review the Yorkie v0.5.1 changelog for any breaking changes or deprecations.
3. Update any relevant documentation to reflect the new version.

Consider implementing an automated process for dependency updates in the future, which could include:

• Automated testing and version bumping
• Changelog generation
• Documentation updates
  This would streamline the update process and reduce the potential for human error.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 0cd2f57 and d41ff3a.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (2)

• .env (1 hunks)
• package.json (2 hunks)

✅ Files skipped from review due to trivial changes (1)

• .env

🧰 Additional context used

🔇 Additional comments (2)

package.json (2)

3-3: LGTM: Version update is consistent with PR objectives.

The version update from "0.5.0" to "0.5.1" aligns with the PR's goal of bumping up Yorkie to v0.5.1. This change follows semantic versioning principles, indicating a patch update.

---

45-45: LGTM: Dependency update matches PR objectives. Verify compatibility.

The update of "yorkie-js-sdk" from "^0.5.0" to "^0.5.1" aligns with the PR's goal. The caret (^) is maintained, allowing for compatible minor and patch updates.

To ensure compatibility, please run the following script:

[hackerwins]

Thanks for your contribution.