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 : version bumped #504

Merged
merged 6 commits into from
Nov 11, 2024

Conversation

iftakharul-islam
Copy link
Contributor

@iftakharul-islam iftakharul-islam commented Nov 11, 2024

  • Updated plugin version
  • Change log added

Summary by CodeRabbit

  • New Features

    • Updated to version 2.6.15, enhancing security and functionality.
  • Bug Fixes

    • Resolved a critical security vulnerability.
    • Addressed user creation issues in new projects.
    • Fixed XSS vulnerabilities and user role management problems.
    • Corrected sub-task duplication issues.
  • Documentation

    • Changelog updated to reflect the latest version and previous fixes.
    • Readme file updated with the new stable tag and version details.

- Updated plugin version
- Change log added
Copy link

coderabbitai bot commented Nov 11, 2024

Caution

Review failed

The pull request is closed.

Walkthrough

The changes in this pull request include updates to the versioning information across several files for the WP Project Manager plugin, specifically moving from version 2.6.14 to 2.6.15. The changelog has been updated to reflect the new version and highlight a security fix. Additionally, the version number in the configuration file and the plugin header comment has been updated to match the new release, while the readme file has been modified to indicate the new stable tag and provide a brief history of recent updates.

Changes

File Change Summary
changelog.txt Updated to include version v2.6.15, highlighting a security fix. Previous version details included.
config/app.php Version updated from '2.6.14' to '2.6.15'.
cpm.php Version updated from '2.6.14' to '2.6.15' in the plugin header comment.
readme.txt Stable tag updated from '2.6.14' to '2.6.15'. Changelog updated with previous version details.
package.json Version updated from '2.6.12' to '2.6.15'.

Poem

🐇 In the garden of code, we hop with glee,
A new version blooms, as bright as can be.
From fourteen to fifteen, we've made our way,
Fixing the bugs, come join the play!
With security tight, and features so fine,
Let's celebrate changes, it's update time! 🎉


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

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Outside diff range and nitpick comments (1)
changelog.txt (1)

Line range hint 1-24: Consider enhancing the changelog format for better readability.

While the current format follows WordPress standards, consider these improvements for better user experience:

  1. Add a brief summary at the top of each version
  2. Group changes by type (Breaking/Security/Feature/Enhancement/Fix)
  3. Include ticket/issue references where applicable

Example format:

 == Changelog ==
 
 = v2.6.15 - Nov 11, 2023 =
+
+This release addresses an important security vulnerability. All users are encouraged to update immediately.
+
+**Security:**
+* Fixed a security vulnerability related to input validation (#504)
+
+**Enhancements:**
+* None in this release
+
+**Bug Fixes:**
+* None in this release
🧰 Tools
🪛 LanguageTool

[typographical] ~3-~3: If you want to indicate numerical ranges or time ranges, consider using an en dash.
Context: == Changelog == = v2.6.15 - Nov 11, 2024 = Fix: Vulnerable secu...

(DASH_RULE)


[typographical] ~7-~7: If you want to indicate numerical ranges or time ranges, consider using an en dash.
Context: ...** Vulnerable security issue. = v2.6.13 - Mar 29, 2024 = Fix: New project's u...

(DASH_RULE)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 7e5ca35 and 4eab97b.

📒 Files selected for processing (4)
  • changelog.txt (1 hunks)
  • config/app.php (1 hunks)
  • cpm.php (1 hunks)
  • readme.txt (1 hunks)
✅ Files skipped from review due to trivial changes (3)
  • config/app.php
  • cpm.php
  • readme.txt
🧰 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.15 - Nov 11, 2024 = Fix: Vulnerable secu...

(DASH_RULE)

🔇 Additional comments (1)
changelog.txt (1)

Line range hint 1-1000: Verify security fix implementation across versions.

The changelog shows multiple security-related fixes across versions. Let's verify the implementation of these fixes.

🧰 Tools
🪛 LanguageTool

[typographical] ~3-~3: If you want to indicate numerical ranges or time ranges, consider using an en dash.
Context: == Changelog == = v2.6.15 - Nov 11, 2024 = Fix: Vulnerable secu...

(DASH_RULE)


[typographical] ~7-~7: If you want to indicate numerical ranges or time ranges, consider using an en dash.
Context: ...** Vulnerable security issue. = v2.6.13 - Mar 29, 2024 = Fix: New project's u...

(DASH_RULE)

changelog.txt Show resolved Hide resolved
@iftakharul-islam iftakharul-islam merged commit 121a2a4 into weDevsOfficial:develop Nov 11, 2024
This was referenced Nov 11, 2024
@coderabbitai coderabbitai bot mentioned this pull request Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant