Bump up Yorkie to v0.6.0

[chacha912]

What this PR does / why we need it?

Bump up Yorkie to v0.6.0

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

• Chores

  • Upgraded the core dependency to version 0.6.0, providing a pathway for enhanced performance, future-proof compatibility, and overall stability.
  • Improved internal sample project configurations to maintain consistency across examples, supporting a smoother development experience.

• Documentation

  • Simplified the authentication configuration alert by removing confusing details, offering clearer guidance on setup and change propagation delays.
  • Added new flags for managing authorization webhook methods in the CLI, enhancing flexibility for users.

[coderabbitai]

Walkthrough

This pull request updates version-related configurations for the Yorkie SDK. The environment variables in the .env file have been incremented from 0.5.7 to 0.6.0, and the URL pointing to the JS SDK library has been correspondingly updated. The upgrade is reflected in both the .env and the package.json dependency for yorkie-js-sdk. Additionally, the alert in the Auth Webhook documentation was simplified by removing two bullet points, and multiple example projects had their FILE_INFO export declarations updated for clarity and consistency.

Changes

File(s)	Change Summary
.env, package.json	Updated Yorkie SDK versions from 0.5.7 to 0.6.0 and adjusted the SDK URL accordingly.
docs/auth-webhook.mdx	Removed two bullet points from the alert in the "Setup and Configuration" section to simplify messaging.
examples/.../fileInfo.ts	Revised export declarations of the FILE_INFO constant across various example projects, standardizing the object structure without altering the underlying data.

Possibly related PRs

• Bump up Yorkie to v0.4.20 #135: Updates environment variables for the Yorkie SDK, including version numbers and URLs.
• Bump up Yorkie to v0.4.23 #137: Addresses version updates for yorkie-js-sdk in configuration files, similar to this PR.
• Bump up Yorkie to v0.5.6 #177: Focuses on modifying the Yorkie SDK version in the environment variables, directly relating to these changes.

Suggested reviewers

• hackerwins

Poem

I'm a clever rabbit, hopping through code,
With each update, my excitement's bestowed.
Versions leap forward like a bound in the night,
Files and docs align, looking ever so right.
In a world of changes, I cheer with delight—
CodeRabbit celebrates under a starry byte!
🐇✨

---

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 generate docstrings to generate docstrings for this PR. (Beta)
• @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: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 721c95e and 92fa292.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (10)

• .env (1 hunks)
• docs/auth-webhook.mdx (1 hunks)
• examples/nextjs-scheduler/fileInfo.ts (1 hunks)
• examples/profile-stack/fileInfo.ts (1 hunks)
• examples/react-tldraw/fileInfo.ts (1 hunks)
• examples/react-todomvc/fileInfo.ts (1 hunks)
• examples/vanilla-codemirror6/fileInfo.ts (1 hunks)
• examples/vanilla-quill/fileInfo.ts (1 hunks)
• examples/vuejs-kanban/fileInfo.ts (1 hunks)
• package.json (1 hunks)

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

• examples/react-tldraw/fileInfo.ts
• examples/vanilla-codemirror6/fileInfo.ts
• examples/react-todomvc/fileInfo.ts
• .env

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: build

🔇 Additional comments (5)

package.json (1)

37-37: Bump dependency version for "yorkie-js-sdk" to v0.6.0

The dependency update from "^0.5.7" to "^0.6.0" is correctly applied, ensuring compatibility with the newer minor version. Please double-check the integration tests and any direct usages of this SDK to confirm that no breaking API changes affect the project.

docs/auth-webhook.mdx (1)

47-49: Streamlined Warning Alert Content

The updated alert now only states, "Configuration changes may take up to 10 minutes to take effect," which simplifies the message by removing the previously confusing bullet points. This offers clearer guidance to users regarding the delay for configuration changes. Just ensure that any critical information removed from the alert is documented elsewhere if needed.

examples/profile-stack/fileInfo.ts (1)

1-2: Well-organized directory structure with clear separation of concerns!

The directory structure effectively separates:

• Public assets (SVG profiles)
• Source code
• Configuration files

examples/vanilla-quill/fileInfo.ts (1)

1-2: Excellent TypeScript implementation with proper type safety!

The directory structure and implementation demonstrate good practices:

• Proper TypeScript configuration
• Clear type definitions
• Well-structured error handling

examples/nextjs-scheduler/fileInfo.ts (1)

1-2: Excellent Next.js implementation following best practices!

The directory structure and implementation demonstrate good practices:

• Proper Next.js app directory structure
• Well-organized React components
• Clean separation of utilities and types

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

docs/cli.mdx (2)

236-240: New Flags Description – Clarity & Consistency Check

The new flags (--auth-webhook-method-add and --auth-webhook-method-rm) and their descriptions are clear. Consider ensuring consistency in terminology (e.g., using "Auth Webhook" uniformly rather than mixing with "authorization-webhook") and clarifying the expected input format for a string array (e.g., whether to pass multiple values using repeated flags or a comma-separated list).

---

257-260: Process Order Explanation for Webhook Methods

The added documentation clarifies that remove operations are processed before add operations, which is helpful for users to understand the behavior. It might be beneficial to briefly mention the rationale behind this ordering (e.g., preventing conflicts or ensuring predictable state changes).

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 92fa292 and 9dbe9c7.

📒 Files selected for processing (2)

• docs/auth-webhook.mdx (1 hunks)
• docs/cli.mdx (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• docs/auth-webhook.mdx

🔇 Additional comments (1)

docs/cli.mdx (1)

261-281: Usage Examples – Verifying Multiple Value Handling

The usage examples for managing webhook methods are comprehensive and easy to follow. Please verify that the CLI tool supports multiple occurrences of the --auth-webhook-method-add flag as shown in the multiple flag example. Alternatively, if a comma-separated list is required, consider updating the examples to reflect the correct usage.

[hackerwins]

Thanks for your contribution.