Update CHANGELOG.md for v0.5.4

[hackerwins]

What this PR does / why we need it:

Update CHANGELOG.md for v0.5.4

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

Release Notes for Version 0.5.4

• New Features

  • Introduced a cmap for distributing mutexes per document.
  • Implemented lock striping for cmap.

• Bug Fixes

  • Corrected the transaction in UpdateAndFindMinSyncedVersionVector.

• Documentation Updates

  • Updated version numbers across various API documentation files to reflect the new version (v0.5.4).

• Version Updates

  • Updated project version from 0.5.3 to 0.5.4 in multiple components, including the Makefile and Chart.yaml.

[coderabbitai]

Walkthrough

This pull request includes updates to multiple files to reflect the new version 0.5.4 for the Yorkie project. Changes are made to the CHANGELOG.md to document new features and fixes, as well as updates to various OpenAPI specification files and the Makefile to indicate the new version. Additionally, the Chart.yaml for the yorkie-cluster application has been updated to match the new version. No functional changes were made to the code or API endpoints.

Changes

File	Change Summary
CHANGELOG.md	Updated to version 0.5.4, added features for cmap mutex distribution and lock striping, and fixed a transaction issue.
Makefile	Updated YORKIE_VERSION from 0.5.3 to 0.5.4.
api/docs/yorkie.base.yaml	Updated version from v0.5.3 to v0.5.4.
api/docs/yorkie/v1/admin.openapi.yaml	Updated version from v0.5.3 to v0.5.4.
api/docs/yorkie/v1/cluster.openapi.yaml	Updated version from v0.5.3 to v0.5.4.
api/docs/yorkie/v1/resources.openapi.yaml	Updated version from v0.5.3 to v0.5.4.
api/docs/yorkie/v1/system.openapi.yaml	Updated version from v0.5.3 to v0.5.4.
api/docs/yorkie/v1/yorkie.openapi.yaml	Updated version from v0.5.3 to v0.5.4.
build/charts/yorkie-cluster/Chart.yaml	Updated version and appVersion from 0.5.3 to 0.5.4.

Possibly related PRs

• Update CHANGELOG.md for v0.4.20 #875: Updates to CHANGELOG.md for version 0.4.20 include changes to the same file as the main PR, indicating a related context of version updates.
• Update CHANGELOG.md for v0.4.22 #890: Updates to CHANGELOG.md for version 0.4.22 also involve changes to the same file, suggesting a similar purpose in documenting version changes.
• Update CHANGELOG.md for v0.4.24 #897: Updates to CHANGELOG.md for version 0.4.24 reflect changes in the same file, maintaining the continuity of version documentation.
• Update CHANGELOG.md for v0.4.25 #912: Updates to CHANGELOG.md for version 0.4.25 involve modifications to the same file, indicating a related context of version updates.
• Update CHANGELOG.md for v0.4.27 #929: Updates to CHANGELOG.md for version 0.4.27 include changes to the same file, suggesting a similar purpose in documenting version changes.
• Update CHANGELOG.md for v0.4.28 #942: Updates to CHANGELOG.md for version 0.4.28 involve changes to the same file, maintaining the continuity of version documentation.
• Update CHANGELOG.md for v0.4.29 #953: Updates to CHANGELOG.md for version 0.4.29 reflect changes in the same file, indicating a related context of version updates.
• Update CHANGELOG.md for v0.4.30 #956: Updates to CHANGELOG.md for version 0.5.0 involve modifications to the same file, suggesting a similar purpose in documenting version changes.
• Update CHANGELOG.md for v0.5.1 #1034: Updates to CHANGELOG.md for version 0.5.1 include changes to the same file, maintaining the continuity of version documentation.
• Update CHANGELOG.md for v0.5.2 #1045: Updates to CHANGELOG.md for version 0.5.2 involve changes to the same file, indicating a related context of version updates.
• Update CHANGELOG.md for v0.5.3 #1049: Updates to CHANGELOG.md for version 0.5.3 reflect changes in the same file, suggesting a similar purpose in documenting version changes.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between c776ae1 and 3348a50.

📒 Files selected for processing (9)

• CHANGELOG.md (1 hunks)
• Makefile (1 hunks)
• api/docs/yorkie.base.yaml (1 hunks)
• api/docs/yorkie/v1/admin.openapi.yaml (1 hunks)
• api/docs/yorkie/v1/cluster.openapi.yaml (1 hunks)
• api/docs/yorkie/v1/resources.openapi.yaml (1 hunks)
• api/docs/yorkie/v1/system.openapi.yaml (1 hunks)
• api/docs/yorkie/v1/yorkie.openapi.yaml (1 hunks)
• build/charts/yorkie-cluster/Chart.yaml (1 hunks)

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

• Makefile
• api/docs/yorkie.base.yaml
• api/docs/yorkie/v1/admin.openapi.yaml
• api/docs/yorkie/v1/cluster.openapi.yaml
• api/docs/yorkie/v1/resources.openapi.yaml
• api/docs/yorkie/v1/system.openapi.yaml
• api/docs/yorkie/v1/yorkie.openapi.yaml
• build/charts/yorkie-cluster/Chart.yaml

🧰 Additional context used

🪛 LanguageTool

CHANGELOG.md

[uncategorized] ~14-~14: Did you mean “document”? If following ‘per’, nouns are often singular.
Context: ...oduce cmap for distributing mutexes per documents by @hackerwins in https://github.com/yo...

(CONFUSION_OF_NNS_NN_UN)

🪛 Markdownlint

CHANGELOG.md

14-14: null
Bare URL used

(MD034, no-bare-urls)

---

15-15: null
Bare URL used

(MD034, no-bare-urls)

---

19-19: null
Bare URL used

(MD034, no-bare-urls)

---

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 46.76%. Comparing base (c776ae1) to head (3348a50).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1054   +/-   ##
=======================================
  Coverage   46.76%   46.76%           
=======================================
  Files          82       82           
  Lines       12001    12001           
=======================================
  Hits         5612     5612           
  Misses       5826     5826           
  Partials      563      563           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.