runtipi version history

- Backup restore now rejects invalid or unsafe archives - Added protection against unsafe symlinks and path traversal - Temporary restore folders are cleaned up on failure

**v4.10.1-beta.3**

**v4.10.1-beta.2**

**v4.10.1-beta.1**

## Release notes **New features** - Start all and stop all apps CLI commands **Improvements** - Tighten filesystem type checks to not follow symlinks when serving public data ## How to update From the root folder of your runtipi install - `./runtipi-cli update v4.10.0` If you are coming from version 3 or lower please follow the [migration guide](https://runtipi.io/docs/reference/breaking-updates#update-from-3xx-to-400)

**v4.10.0-beta.1**

## Release notes **Improvements** - Add an option to add trusted IP/CIDRs for forwarded headers. This makes Cloudflare tunnels and other VPN setups possible when the link between the proxy and runtipi is not using the same protocol. Error: `Invalid request origin` See [docs](https://runtipi.io/docs/learn/troubleshooting#dashboard-behind-a-reverse-proxy-or-tunnel) ## How to update From the root folder of your runtipi install - `./runtipi-cli update v4.9.3` If you are coming from version 3 or lower please follow the [migration guide](https://runtipi.io/docs/reference/breaking-updates#update-from-3xx-to-400)

**v4.9.2-beta.1**

## Release notes **Improvements** - Sensitive values are now automatically redacted from application logs - Swagger API documentation is no longer exposed in production environments, reducing unnecessary production surface area. - Set `maxResponseBodySize` in traefik forward auth middleware **Bug fixes** - Marketplace app images no longer count against API throttling limits. This should prevent app store images from failing to load or returning rate-limit errors when browsing many apps. ## How to update From the root folder of your runtipi install - `./runtipi-cli update v4.9.1` If you are coming from version 3 or lower please follow the [migration guide](https://runtipi.io/docs/reference/breaking-updates#update-from-3xx-to-400)

This is an automated release. It is not stable and is used solely by developers to test new features in a production-like environment.