chore(main): release 0.20.0

[dreulavelle]

🤖 I have created a release beep boop

0.20.0 (2025-03-19)

Features

• add back button to manual scrape popup (#199) (037a562)
• multi select for actions which should impact multiple items (#197) (a9e693c)

Bug Fixes

• add repair symlinks button (2fe398c)
• add year in tmdb search results (bb58d45)
• manual scraping responsiveness (ed9fc24)

---

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

• New Features

  • Added a back button for a more intuitive manual scraping experience.
  • Introduced multi-select options to enable actions on multiple items simultaneously.

• Bug Fixes

  • Improved repair functionalities and search result details.
  • Enhanced responsiveness for manual scraping interactions.

• Chore

  • Updated the application version to 0.20.0.

[coderabbitai]

📝 Walkthrough

Walkthrough

A new release entry for version 0.20.0 has been added. The project's changelog now includes a feature entry for the addition of a back button to the manual scrape popup (linked to issue #199 and commit 037a562), a multi-select feature for actions impacting multiple items (linked to issue #197 and commit a9e693c), and bug fix entries detailing the addition of the year in TMDB search results (linked to commit bb58d45), a repair symlinks button (linked to commit 2fe398c), and improved manual scraping responsiveness (linked to commit ed9fc24). The version number in version.txt has been updated from 0.19.0 to 0.20.0.

Changes

File(s)	Change Summary
CHANGELOG.md	Added a new version entry for 0.20.0 with feature entries for adding a back button to the manual scrape popup (issue #199, commit 037a562) and a multi-select feature for actions impacting multiple items (issue #197, commit a9e693c), along with bug fix entries for adding the year in TMDB search results (commit bb58d45), adding a repair symlinks button (commit 2fe398c), and improving manual scraping responsiveness (commit ed9fc24).
version.txt	Updated the version number from 0.19.0 to 0.20.0.

Tip

⚡🧪 Multi-step agentic review comment chat (experimental)

• We're introducing multi-step agentic chat in review comments. This experimental feature enhances review discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments.
  - To enable this feature, set early_access to true under in the settings.

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between d28b906 and fca3b11.

📒 Files selected for processing (2)

• CHANGELOG.md (1 hunks)
• version.txt (1 hunks)

🧰 Additional context used

🪛 markdownlint-cli2 (0.17.2)

CHANGELOG.md

5-5: Multiple consecutive blank lines
Expected: 1; Actual: 2

(MD012, no-multiple-blanks)

---

11-11: Multiple consecutive blank lines
Expected: 1; Actual: 2

(MD012, no-multiple-blanks)

🔇 Additional comments (5)

version.txt (1)

1-2: Version Update Confirmed.
The version number has been correctly updated to 0.20.0 in this file. No issues found with the change.

CHANGELOG.md (4)

1-4: New Version Entry and Release Date.
The header for version 0.20.0 is correctly formatted and includes the release date (2025-03-19). The link to the diff compared with version 0.19.0 is intact.

---

4-5: Markdown Formatting: Extra Blank Lines.
There are consecutive blank lines between the version header and the following section. To comply with the markdown lint guidelines (MD012), please remove the extra blank line so that only one blank line remains.

🧰 Tools

🪛 markdownlint-cli2 (0.17.2)

5-5: Multiple consecutive blank lines
Expected: 1; Actual: 2

(MD012, no-multiple-blanks)

---

6-10: Features Section: New Feature Entries.
The "### Features" section clearly documents the two new features—the back button for the manual scrape popup and the multi-select option for actions—with correct references to issue numbers and commit hashes. The formatting is clear and consistent.

---

12-17: Bug Fixes Section: Detailed and Consistent.
The "### Bug Fixes" block accurately lists the bug fixes along with the corresponding commit references. The documentation for the repair symlinks button, the inclusion of the year in TMDB search results, and the manual scraping responsiveness improvements aligns well with the PR objectives.

---

🪧 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.
• @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: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between bb58d45 and 5654cec.

📒 Files selected for processing (2)

• CHANGELOG.md (1 hunks)
• version.txt (1 hunks)

🧰 Additional context used

🪛 markdownlint-cli2 (0.17.2)

CHANGELOG.md

5-5: Multiple consecutive blank lines
Expected: 1; Actual: 2

(MD012, no-multiple-blanks)

🔇 Additional comments (3)

version.txt (1)

1-2: Version Update Verified.

The version number has been correctly updated to 0.19.1, and it is consistent with the new release as intended.

CHANGELOG.md (2)

3-4: New Version Entry Added Correctly.

The new release entry for version 0.19.1 is properly formatted with the release date and provides a link to the changes compared to the previous release.

---

6-8: Bug Fix Entry Documented.

The bug fix addressing the addition of the year in TMDB search results is clearly documented with the correct commit reference ([bb58d45]). This entry effectively communicates the purpose of the fix.