The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "privaxy-aarch64-unknown-linux-gnu", "privaxy-deb-aarch64-unknown-linux-gnu", "privaxy-deb-x86_64-unknown-linux-gnu", "privaxy-x86_64-unknown-linux-gnu". Please update your workflow to use v4 of the artifact actions. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/cache@v3, actions-rs/toolchain@v1, actions/setup-node@v3, actions-rs/cargo@v1, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Unexpected input(s) 'working-directory', valid inputs are ['command', 'toolchain', 'args', 'use-cross']

profiles for the non root package will be ignored, specify profiles at the workspace root:

virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`

unused import: `crate::configuration`

field `data` is never read

`privaxy` (lib) generated 2 warnings (run `cargo fix --lib -p privaxy` to apply 1 suggestion)

profiles for the non root package will be ignored, specify profiles at the workspace root:

virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`

unused import: `crate::configuration`

field `data` is never read

`privaxy` (lib) generated 2 warnings (run `cargo fix --lib -p privaxy` to apply 1 suggestion)

license field is missing in Cargo.toml

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

package `libc v0.2.154` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked

profiles for the non root package will be ignored, specify profiles at the workspace root:

virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`

unused import: `crate::button`

unused import: `crate::save_button::BASE_BUTTON_CSS`

unused imports: `save_button`, `submit_banner`

unused import: `crate::success_banner`

unused import: `Callback`

methods `get_filters` and `has_filter` are never used

enum `SettingType` is never used