chore(main): release 1.5.1

[dreulavelle]

🤖 I have created a release beep boop

1.5.1 (2024-11-20)

Bug Fixes

• tidied adult keywords (3e6e3b2)

---

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

• New Features

  • Version 1.5.1 released, enhancing the application's functionality.

• Bug Fixes

  • Resolved issues related to tidying adult keywords.

• Documentation

  • Updated changelog to reflect new version and changes from previous releases.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request includes updates to the CHANGELOG.md and pyproject.toml files for the project "parsett." The CHANGELOG.md now features a new version entry for version 1.5.1, released on November 20, 2024, which documents a bug fix related to tidying adult keywords. The pyproject.toml file reflects an increment in the version number from 1.5.0 to 1.5.1, while the dependency on the regex package remains unchanged.

Changes

File	Change Summary
CHANGELOG.md	Added version 1.5.1 entry; documented a bug fix for tidying adult keywords; included historical entries for previous versions.
pyproject.toml	Updated version from 1.5.0 to 1.5.1; dependency on regex package noted as unchanged.

Possibly related PRs

• chore(main): release 1.5.0 #31: The main PR is directly related as both involve the release of version 1.5.0, with the main PR documenting a bug fix concerning adult keywords, which aligns with the new feature of adult parsing introduced in PR chore(main): release 1.5.0 #31.

Suggested labels

autorelease: pending

Poem

🐇 In the garden of code, a new version blooms,
With tidied keywords, dispelling the glooms.
From five point oh to one point five one,
Each change a hop, each fix a fun run!
So let’s celebrate with carrots and cheer,
For parsett's bright future is finally here! 🌼

Warning

Rate limit exceeded

@dreulavelle has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 24 minutes and 25 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 3e6e3b2 and a4c6e60.

---

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.68%. Comparing base (3e6e3b2) to head (a4c6e60).
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #33   +/-   ##
=======================================
  Coverage   92.68%   92.68%           
=======================================
  Files           4        4           
  Lines         697      697           
  Branches       62       62           
=======================================
  Hits          646      646           
  Misses         38       38           
  Partials       13       13           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

---

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests

[dreulavelle]

🤖 Created releases:

• v1.5.1
  🌻