next milestone

[kworr]

Summary by CodeRabbit

• Chores

  • Swapped an unused dependency for a lighter HTML-encoding library.
  • Adjusted CI trigger to run only on pull requests.

• Bug Fixes

  • Improved validation to better detect and block Telegram pre/code closing tags and to return safely escaped HTML.

• Style

  • Improved error log formatting for clearer messages.

• Tests

  • Updated tests to reflect new validation and escaping behaviour.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Warning

Rate limit exceeded

@kworr has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 0 minutes and 56 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between e1147a2 and cc4dc53.

📒 Files selected for processing (1)

• src/mail.rs

📝 Walkthrough

Walkthrough

Replaces scraper-based HTML validation with a regex-based closing-tag check and HTML-escaping, updates Cargo.toml dependencies accordingly, adjusts a log formatting call in mail.rs, and updates tests to match the new validation/escaping behaviour.

Changes

Cohort / File(s)	Summary
Dependencies Cargo.toml	Removed scraper = "0.25.0" and added html-escape = "0.2.13".
Validation logic src/utils.rs	Introduced pub static ref RE_CLOSING regex; changed validate signature to return Cow<'_, str>; replaced scraper-based HTML fragment parsing with regex check for Telegram </pre>/</code> and HTML-escaping via html_escape::encode_text.
Logging src/mail.rs	Changed relay_mail error log formatting from {:?} (Debug) to {} (Display).
Tests src/tests.rs	Updated assertions to expect HTML-escaped output and adjusted panic message to match new "Telegram closing tag found." error text.
CI workflow .github/workflows/rust-clippy.yml	Removed push trigger and concurrency cancellation; workflow now triggers on pull_request only.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• next milestone #7: Modifies src/utils.rs validation/encoding logic in a manner directly related to replacing scraper-based parsing with regex/escaping approaches.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'next milestone' is vague and does not clearly summarise the specific changes made in this pull request, which involve dependency updates, validation logic refactoring, and workflow modifications.	Replace with a more descriptive title that highlights the primary change, such as 'Replace HTML parsing with regex-based validation and HTML escaping' or 'Refactor HTML validation logic and update dependencies'.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch master

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.