Changelog for v2.6.21

[iftakharul-islam]

Summary by CodeRabbit

• Documentation
  • Release notes updated with version v2.6.21.
• Bug Fixes
  • Resolved issues with project category organization.
  • Fixed display problems affecting special characters in task types.
• Version Updates
  • Project version updated to 2.6.21 across various files.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changelog has been updated with a new version entry for v2.6.21, released on February 18, 2025. This update includes two fixes: one for a bug in the project category organization and another for issues with the display of special characters in task types. The previous version, v2.6.20, remains unchanged, and there are no modifications to exported or public entity declarations.

Changes

File(s)	Change Summary
changelog.txt	Added new version entry v2.6.21 (Feb 18, 2025) with fixes for project category bug and special character display issues.
config/app.php	Updated version from '2.6.17' to '2.6.21'.
cpm.php	Updated version from '2.6.20' to '2.6.21'.
package.json	Updated version from '2.6.20' to '2.6.21'.
readme.txt	Updated stable tag from '2.6.20' to '2.6.21' and included changelog for version 2.6.21.

Possibly related PRs

• v2.6.17 Change log updated #522: Related to updates of version numbers across multiple files, consistent with this version update.
• Update plugin version and added changelog #501: Involves updating the version number in the same files, albeit to different version numbers.
• tested upto 6.7 & version bump #511: Both involve updating the version number in the same files, reflecting a version increment for the project.

Suggested reviewers

• MdAsifHossainNadim

Poem

I'm a bouncy rabbit, quick on my feet,
Celebrating fixes that are pretty neat!
v2.6.21 hops in with a magic sway,
Bugs disappear like dusk's gray.
With every line fixed, I munch a carrot in delight!
🥕🐇

---

📜 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 3e1ad2f and 0280768.

📒 Files selected for processing (4)

• config/app.php (1 hunks)
• cpm.php (1 hunks)
• package.json (1 hunks)
• readme.txt (2 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

changelog.txt (1)

3-4: Version Header Formatting:
The new version entry ("= v2.6.21 - Feb 18, 2025 =") is clearly delineated and follows the established pattern of the changelog. One minor stylistic suggestion: consider using an en dash (–) instead of a hyphen (-) in the date if your style guidelines recommend it (e.g., "Feb 18, 2025").

🧰 Tools

🪛 LanguageTool

[typographical] ~3-~3: If you want to indicate numerical ranges or time ranges, consider using an en dash.
Context: == Changelog == = v2.6.21 - Feb 18, 2025 = Fix: Project Categor...

(DASH_RULE)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 06898b2 and 3e1ad2f.

📒 Files selected for processing (1)

• changelog.txt (1 hunks)

🧰 Additional context used

🪛 LanguageTool

changelog.txt

[typographical] ~3-~3: If you want to indicate numerical ranges or time ranges, consider using an en dash.
Context: == Changelog == = v2.6.21 - Feb 18, 2025 = Fix: Project Categor...

(DASH_RULE)

🔇 Additional comments (1)

changelog.txt (1)

5-6: Fixes Description Clarity:
The two fixes are concisely stated and clearly express the intent:

• "Fix: Project Category bug for seamless organization."
• "Fix: Resolved Task Type special character display issues."

These descriptions are consistent with previous entries; however, if possible, consider linking them to corresponding issue numbers or providing a tad more detail for future reference.