Update CHANGELOG.md for v0.1.32

[devleejb]

What this PR does / why we need it:

• Update CHANGELOG.md for v0.1.32

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

• Chores

  • Updated release version to 0.1.32 with a revised release date.

• Bug Fixes

  • Applied a fix to enhance dependency configuration, improving overall system reliability.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request updates the version numbers from 0.1.31 to 0.1.32 across multiple package files. The CHANGELOG.md has been revised to reflect the new version, an updated release date, and a new entry describing a fix for a Dockerfile issue with pnpm and corepack (credited to @krapie). Older version entries remain present but are reordered. All related package files (root, backend, desktop, and frontend) have their version fields updated accordingly.

Changes

Files	Change Summary
CHANGELOG.md	Updated version from 0.1.31 to 0.1.32, changed release date from 2024-02-18 to 2025-02-22, and added a fix entry for Dockerfile issues with pnpm and corepack (by @krapie).
backend/package.json, desktop/package.json, frontend/package.json, package.json	Updated version field from 0.1.31 to 0.1.32 across all package definition files.

Possibly related PRs

• Update CHANGELOG.md for v0.1.16 #382: Updates the CHANGELOG.md with version and ordering modifications, closely related to this PR’s changelog update.
• Update CHANGELOG.md for v0.1.31 #454: Involves version updates in both CHANGELOG.md and package files, similar to the changes implemented here.
• Update version to v0.1.2 #295: Focuses on updating the version number in backend/package.json, aligning with the version updates in this PR.

Poem

I'm a bunny in the code, hopping all around,
Leaping to new versions with a joyful sound.
From 0.1.31 to 0.1.32 the numbers now align,
Docker fix and changelog tweaks, all looking fine!
With carrots and commits, I celebrate this day,
Hoppy code and rapid updates lead the way!

---

📜 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 134d7a2 and 8a28146.

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