Release/1.3.0 rc5

[gin0115]

Changes proposed in this Pull Request

• Finalises the changes for 1.3.0-RC5

This pull request introduces several updates to the Wayback Link Fixer plugin, including enhancements to functionality, dependency updates, and version adjustments. The most significant changes involve the addition of a new function to exclude links from the current site, updates to test cases to validate this functionality, and modifications to plugin metadata and dependencies.

Functional Enhancements:

• Added a new function wpcomsp_wayback_link_fixer_is_current_site_link in functions.php to check if a URL belongs to the current site. This ensures links from the current site are excluded from processing.
• Updated the get_links method in Content_Scanner.php to exclude current site links from the list of scanned links.

Testing Improvements:

• Added a new test case test_exclude_links_from_current_site in Test_Content_Scanner.php to verify that links from the current site are excluded. Included a data provider to test various scenarios for site links.

Dependency Updates:

• Updated composer.json dependencies, including bumping versions for wp-cli/i18n-command, php-stubs/wordpress-stubs, roots/wordpress, and wp-phpunit/wp-phpunit to align with the latest releases.

Metadata Adjustments:

• Updated plugin version to 1.3.0-RC5 in package.json and wayback-link-fixer.php. [1] [2] [3]
• Modified README.md to reflect updated PHP requirements (from 8.0 to 7.4) and changed terminology from BITROT to LINKROT. [1] [2]

Testing instructions

Mentions #

Summary by CodeRabbit

• New Features
  • Improved filtering to exclude links from the current site when scanning content for external links.
• Bug Fixes
  • Enhanced accuracy in identifying and excluding current site links from processing.
• Documentation
  • Updated user-facing descriptions, help texts, and messages for greater clarity and accuracy throughout the plugin interface.
  • Corrected terminology and updated version requirements in documentation.
• Tests
  • Added tests to verify exclusion of current site links during content scanning.
• Chores
  • Updated development dependencies and version numbers in project files.

[coderabbitai]

Walkthrough

This update introduces several changes across the project. The minimum required PHP version in the documentation was lowered from 8.0 to 7.4, and version numbers were incremented in multiple files to reflect a new release candidate. Composer development dependencies were updated to more recent versions. A new function was added to identify links belonging to the current site, and the content scanner was modified to exclude such links from processing. Corresponding unit tests were added to verify this exclusion logic. The translation template received extensive updates to user-facing strings for improved clarity and accuracy. No exported or public entity signatures were changed except for the addition of new test methods and a new utility function.

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 0f4f3b3 and 5802b77.

⛔ Files ignored due to path filters (1)

• composer.lock is excluded by !**/*.lock

📒 Files selected for processing (8)

• README.md (2 hunks)
• composer.json (1 hunks)
• functions.php (1 hunks)
• languages/wayback-link-fixer.pot (10 hunks)
• package.json (2 hunks)
• src/Processor/Content_Scanner.php (1 hunks)
• tests/Processor/Test_Content_Scanner.php (1 hunks)
• wayback-link-fixer.php (2 hunks)

---

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Join our Discord community for assistance with any issues or questions.

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 sequence diagram to generate a sequence diagram of the changes in this 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.