Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update CHANGELOG.md for v0.1.8 #328

Merged
merged 1 commit into from
Sep 1, 2024
Merged

Update CHANGELOG.md for v0.1.8 #328

merged 1 commit into from
Sep 1, 2024

Conversation

devleejb
Copy link
Member

@devleejb devleejb commented Sep 1, 2024

What this PR does / why we need it:

Update CHANGELOG.md for v0.1.8

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 application version to 0.1.8, indicating minor enhancements and improvements.
  • Bug Fixes

    • Downgraded the yorkie-js-sdk dependency to address potential issues with the previous version.
    • Disabled retry logic for handling 401 errors during login, improving error handling and user experience related to unauthorized access.

Copy link
Contributor

coderabbitai bot commented Sep 1, 2024

Caution

Review failed

The pull request is closed.

Walkthrough

The changes involve updating the version numbers for both the backend and frontend projects from 0.1.7 to 0.1.8. Additionally, the yorkie-js-sdk dependency in the backend has been downgraded to version 0.4.27, and the retry logic for handling 401 errors during login has been disabled. These modifications reflect adjustments in dependency management and error handling.

Changes

Files Change Summary
backend/package.json Version updated from 0.1.7 to 0.1.8.
frontend/package.json Version updated from 0.1.7 to 0.1.8.
CHANGELOG.md Added entry for version 0.1.8, noting the downgrade of yorkie-js-sdk and disabling of retry logic for 401 errors.

Poem

🐰 In fields of change, I hop with glee,
Version numbers rise, oh joy for me!
A downgrade here, a logic shift,
In code we trust, our spirits lift!
With every patch, we dance and play,
A brighter path, come what may! 🌼


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
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.

@devleejb devleejb merged commit 01f5744 into main Sep 1, 2024
3 checks passed
@devleejb devleejb deleted the v0.1.8 branch September 1, 2024 13:36
@coderabbitai coderabbitai bot mentioned this pull request Sep 12, 2024
2 tasks
@coderabbitai coderabbitai bot mentioned this pull request Oct 14, 2024
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

1 participant