Skip to content

Update transmission to version 4.1.1#4950

Merged
al-lac merged 1 commit intomasterfrom
update-transmission-4.1.1
Mar 2, 2026
Merged

Update transmission to version 4.1.1#4950
al-lac merged 1 commit intomasterfrom
update-transmission-4.1.1

Conversation

@al-lac
Copy link
Collaborator

@al-lac al-lac commented Mar 2, 2026

🤖 This is an automated pull request to update transmission to version 4.1.1. This PR must be reviewed and tested before merging.

Auto-generated update considerations:

  • tcp-enabled and udp-enabled settings in settings.json are deprecated; replaced by preferred_transports — existing configurations using these keys should be updated
  • cache-size-mb setting renamed to cache_size_mib in settings.json — existing configurations referencing the old key will need to be updated
  • peer_socket_tos setting renamed to peer_socket_diffserv in settings.json — existing configurations referencing the old key will need to be updated
  • RPC API has been updated to JSON-RPC 2.0 compliance; third-party tools or scripts interacting with the RPC endpoint may need updates
  • torrent_get.wanted now returns an array of booleans instead of integers in the JSON-RPC API — any scripts or integrations parsing this field may break
  • Encryption mode values in settings.json and RPC are now serialized to a consistent set of strings — existing stored values may differ from the new format
  • A 4.1.0 RPC change that returned floating-point numbers for speed limit fields (instead of integers) was reverted in 4.1.1 — third-party integrations affected by the 4.1.0 change should re-verify behavior
  • New files are now assigned a file mode based on the process umask defined in settings.json — file permission behavior may change on upgrade
  • session_get.rpc_version and session_get.rpc_version_minimum are deprecated in favor of session_get.rpc_version_semver in RPC — scripts relying on the old fields should be updated
  • torrent-get.manualAnnounceTime RPC field is deprecated — integrations using this field should plan for its removal
  • Daemon log timestamps changed to local ISO 8601 format — any log parsing tools expecting the previous format may need adjustment

Original GitHub release notes

@github-actions
Copy link

github-actions bot commented Mar 2, 2026

🎉   Linting finished with no errors or warnings   🎉

Thank you for your submission! This is an automated linter that checks for common issues in pull requests to the Umbrel App Store.

Please review the linting results below and make any necessary changes to your submission.

Linting Results

Severity File Description
ℹ️ transmission/docker-compose.yml External port mapping "51413:51413":
Port mappings may be unnecessary for the app to function correctly. Docker's internal DNS resolves container names to IP addresses within the same network. External access to the web interface is handled by the app_proxy container. Port mappings are only needed if external access is required to a port not proxied by the app_proxy, or if an app needs to expose multiple ports for its functionality (e.g., DHCP, DNS, P2P, etc.).
ℹ️ transmission/docker-compose.yml External port mapping "51413:51413/udp":
Port mappings may be unnecessary for the app to function correctly. Docker's internal DNS resolves container names to IP addresses within the same network. External access to the web interface is handled by the app_proxy container. Port mappings are only needed if external access is required to a port not proxied by the app_proxy, or if an app needs to expose multiple ports for its functionality (e.g., DHCP, DNS, P2P, etc.).
ℹ️ transmission/docker-compose.yml Potentially using unsafe user in service "widget-server":
The default container user "root" can lead to security vulnerabilities. If you are using the root user, please try to specify a different user (e.g. "1000:1000") in the compose file or try to set the UID/PUID and GID/PGID environment variables to 1000.

Legend

Symbol Description
Error: This must be resolved before this PR can be merged.
⚠️ Warning: This is highly encouraged to be resolved, but is not strictly mandatory.
ℹ️ Info: This is just for your information.

@al-lac
Copy link
Collaborator Author

al-lac commented Mar 2, 2026

🤖 This is an automated summary of installation tests for transmission:

  • ✅ App successfully installed in umbrel-dev instance
  • ✅ App successfully listed in umbrel.yaml
  • ✅ App UI successfully returns a 200 status code
  • 📸 Screenshot of the app:
    App Screenshot

This PR must still be reviewed and tested before merging.

@al-lac
Copy link
Collaborator Author

al-lac commented Mar 2, 2026

Tested update on Umbrel dev instance.

@al-lac al-lac merged commit 7f2850f into master Mar 2, 2026
1 check passed
@al-lac al-lac deleted the update-transmission-4.1.1 branch March 2, 2026 15:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant