⬆️ Update sabnzbd/sabnzbd to v4.3.3

[renovate]

This PR contains the following updates:

Package	Update	Change
sabnzbd/sabnzbd	patch	4.3.2 -> 4.3.3

---

Release Notes

sabnzbd/sabnzbd (sabnzbd/sabnzbd)

v4.3.3: SABnzbd 4.3.3

Compare Source

Release Notes - SABnzbd 4.3.3

This is the third bug fix release of SABnzbd 4.3.0.

Bug fixes and changes since 4.3.2

• Reduced chance of jobs getting stuck at 99%.
• Prevent crash in case of invalid articles.
• Correct handling of empty or Default category when adding a job.
• History API-output could contain inconsistent variable types.
• Skip external IPv6 check if only link local addresses are available.
• Shortened timeouts when resolving addresses during checks.
• Windows: Could not repair or extract on ARM platforms.
• Windows: Add file version information to installer.

Bug fixes and changes since 4.3.1

• Added Special option disable_archive for jobs to always be permanently deleted.
• Specific AppRise notifications could fail to send.
• Update of the article decoder core (rapidyenc).
• Windows: After some time the interface would no longer load.
• Windows: Custom shortcuts would be removed by the installer.
• Windows/macOS: Updated Unrar to 7.01 and 7zip to 24.05.

Key changes since 4.2.0

• Archive:

  • When jobs are removed from the History, they are moved to the Archive.
  • Keep your History clean and still be able to reliably use Duplicate Detection.

• Apprise Integrated:

  • Send notifications using Apprise to almost any notification service.
  • Supported notifications: https://github.com/caronc/apprise/wiki
  • Notification Script SABnzbd-notify.py is no longer needed.

• Added IPv6-staging option:

  • Enable ipv6_staging in Config - Specials to get additional IPv6 features:
    • Add IPv6 hostnames during address selection.
    • Internet Bandwidth is measured separately for IPv4 and IPv6.

• Other:

  • The text output format is removed from the API, json is the default.
  • Handling of multiple inputs to several API methods was improved.
  • File browser dialog is available to select file paths in the Config.
  • Users will be warned if they configure an Indexer as a Server.
  • Added SAB_API_KEY and SAB_API_URL to script environment variables.
  • Windows/macOS: Updated Python to 3.12.3, Multipar to v1.3.3.2,
    Unrar to 7.00 and 7zip to 24.03.

Bug fixes since 4.2.0

• Incorrect warnings of unknown status codes could be thrown.
• Watched Folder would not work if Socks5 proxy was active.
• Prevent crash on invalid Server Expiration Date.
• Windows: Installer could create duplicate shortcuts.

Upgrade notices

• You can directly upgrade from version 3.0.0 and newer.
• Upgrading from older versions will require performing a Queue repair.
• Downgrading from version 4.2.0 or newer to 3.7.2 or older will require
  performing a Queue repair due to changes in the internal data format.

Known problems and solutions

• Read ISSUES.txt or https://sabnzbd.org/wiki/introduction/known-issues

About

SABnzbd is an open-source cross-platform binary newsreader.
It simplifies the process of downloading from Usenet dramatically, thanks to its web-based
user interface and advanced built-in post-processing options that automatically verify, repair,
extract and clean up posts downloaded from Usenet.

(c) Copyright 2007-2024 by The SABnzbd-Team (sabnzbd.org)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Walkthrough

The change involves updating the SABnzbd Dockerfile to reflect a new version of the SABnzbd application, moving from version 4.3.2 to 4.3.3. This upgrade may introduce enhancements, bug fixes, or new features, while maintaining the existing structure of the Dockerfile. The revision is part of routine maintenance to ensure the application runs with the latest improvements.

Changes

File	Change Summary
sabnzbd/Dockerfile	Updated SABNZBD_VERSION from 4.3.2 to 4.3.3

Poem

🐇 In the burrow deep, we cheer with glee,
A new version hops in, 4.3.3!
With fixes and tweaks, it’s better than before,
Bugs be gone, let’s dance and explore!
So raise your carrots, let joy take flight,
SABnzbd shines, all is just right! 🌟

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between ba52638 and 4e9f8d0.

Files selected for processing (1)

• sabnzbd/Dockerfile (1 hunks)

Files skipped from review due to trivial changes (1)

• sabnzbd/Dockerfile