Update CHANGELOG.md for v0.1.31

[devleejb]

What this PR does / why we need it:

• Update CHANGELOG.md for v0.1.31

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

• Revert
  • Reinstated key functionality that had been removed in a previous update.
• Chores
  • Synchronized project versions by updating all components to version 0.1.31.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request updates the project to version 0.1.31. The CHANGELOG.md now includes a new section for version 0.1.31 dated 2024-02-18, with a "Fixed" category that documents the reversion of the removal of the SPA GitHub Pages script from index.html, originally introduced in pull request #449 by @devleejb. In addition, all package manifest files—backend, desktop, frontend, and the root package.json—have their version updated from 0.1.30 to 0.1.31.

Changes

File(s)	Change Summary
CHANGELOG.md	Added new section for v0.1.31 with a "Fixed" category documenting the reversion of the SPA GitHub Pages script removal.
backend/package.json, desktop/package.json, frontend/package.json, package.json	Package version updated from 0.1.30 to 0.1.31.

Possibly related PRs

• Update CHANGELOG.md for v0.1.30 #453: Involves changes to revert the removal of the SPA GitHub Pages script from index.html.
• Update CHANGELOG.md for v0.1.26 #419: Contains modifications to CHANGELOG.md that document version updates, aligning with the current changelog update.
• Update CHANGELOG.md for v0.1.23 #408: Updates the CHANGELOG.md for a previous version with a reversion, paralleling the current version documentation.

Poem

Hoppin' through the code, I gleefully sing,
Version 0.1.31 brings a fresh spring.
The lost script returns from yonder past,
In CHANGELOG lines, its fix is cast.
A rabbit's cheer in lines of code so neat,
Carrots and commits—what a treat! 🐇🌟

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 95d8a8f and f56fa2d.

📒 Files selected for processing (5)

• CHANGELOG.md (1 hunks)
• backend/package.json (1 hunks)
• desktop/package.json (1 hunks)
• frontend/package.json (1 hunks)
• package.json (1 hunks)

---

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.