Update CHANGELOG.md for v0.1.17

[devleejb]

What this PR does / why we need it:

• Update CHANGELOG.md for v0.1.17

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

  • Version 0.1.17 released, featuring updates to changelog and versioning.
  • Devtools have been disabled for improved performance.
  • SourceMap for Sentry has been activated.

• Bug Fixes

  • Resolved TypeScript version conflict with ESLint.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes in this pull request include an update to the version number across multiple package.json files and the CHANGELOG.md. The version has been incremented from 0.1.16 to 0.1.17, with the changelog detailing two significant updates: the disabling of devtools and the activation of SourceMap for Sentry, along with a resolution of a TypeScript version conflict with ESLint. The overall structure of the changelog adheres to established formatting practices.

Changes

File	Change Summary
CHANGELOG.md	Added new version entry [0.1.17] - 2024-10-25 detailing changes regarding devtools and Sentry.
backend/package.json	Updated version from 0.1.16 to 0.1.17.
frontend/package.json	Updated version from 0.1.16 to 0.1.17.
package.json	Updated version from 0.1.16 to 0.1.17.

Possibly related PRs

• Update CHANGELOG.md for v0.1.3 #303: Updates the CHANGELOG.md for version 0.1.3, relevant due to changes in the same file.
• Update CHANGELOG.md for v0.1.4 #309: Updates the CHANGELOG.md for version 0.1.4, related for the same reason.
• Update CHANGELOG.md for v0.1.7 #324: Updates the CHANGELOG.md for version 0.1.7, maintaining relevance due to changes in the same file.
• Update CHANGELOG.md for v0.1.8 #328: Updates the CHANGELOG.md for version 0.1.8, related as it involves the same file.
• Update CHANGELOG.md for v0.1.9 #330: Updates the CHANGELOG.md for version 0.1.9, relevant for the same reason.
• Update CHANGELOG.md for v0.1.10 #335: Updates the CHANGELOG.md for version 0.1.10, maintaining relevance due to changes in the same file.
• Update CHANGELOG.md for v0.1.11 #343: Updates the CHANGELOG.md for version 0.1.11, which is related as it involves the same file.
• Update CHANGELOG.md for v0.1.13 #358: Updates the CHANGELOG.md for version 0.1.13, relevant for the same reason.

🐇 In the meadow, changes bloom,
A version new dispels the gloom.
With devtools off, and Sentry bright,
Our code now shines, a joyful sight!
Hopping forth, we celebrate,
Version 0.1.17, oh, how great! 🌼

---

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.