Update CHANGELOG.md for v0.1.16

[devleejb]

What this PR does / why we need it:

• Update CHANGELOG.md for v0.1.16

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

  • Updated the CHANGELOG.md to include version 0.1.16 with details on recent changes.

• Bug Fixes

  • Updated yorkie-js-sdk to versions 0.5.1, 0.5.2, and 0.5.3 for improved functionality.

• Chores

  • Incremented version numbers across package.json files for backend, frontend, and root project to 0.1.16.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request introduces updates to the versioning of several components within the project, specifically changing the version number from 0.1.15 to 0.1.16 across multiple package.json files. Additionally, the CHANGELOG.md file has been updated to reflect these changes, including multiple updates to the yorkie-js-sdk to versions 0.5.1, 0.5.2, and 0.5.3, along with a significant code refactor related to Yorkie Intelligence.

Changes

File	Change Summary
CHANGELOG.md	Updated to version 0.1.16 with entries for yorkie-js-sdk updates and a model type removal.
backend/package.json	Version updated from 0.1.15 to 0.1.16.
frontend/package.json	Version updated from 0.1.15 to 0.1.16.
package.json	Version updated from 0.1.15 to 0.1.16.

Possibly related PRs

• Update yorkie-js-sdk to v0.5.1 #369: This PR updates the yorkie-js-sdk to version 0.5.1, which is directly related to the main PR's changelog update that includes multiple updates to the yorkie-js-sdk, specifically mentioning versions 0.5.1, 0.5.2, and 0.5.3.
• Update yorkie-js-sdk to v0.5.2 #380: This PR updates the yorkie-js-sdk to version 0.5.2, which is also directly related to the main PR's changelog update that lists the same version among the updates made.

Poem

In the code where bunnies play,
A version change has come our way.
From fifteen to sixteen, we hop along,
With Yorkie updates, we sing our song!
Changelog bright, with changes so neat,
A refactor here makes our project sweet! 🐇✨

---

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.