Below you will find pages that utilize the taxonomy term “RobertRautenbach”
April 22, 2026
rust-affected
Version updated for https://github.com/RobertRautenbach/rust-affected to version v4.0.2.
This action is used across all versions by ? repositories. Action Type This is a Docker action.
Go to the GitHub Marketplace to find the latest changes.
Action Summary The rust-affected GitHub Action analyzes changes in a Rust workspace to identify which packages are impacted based on the Cargo dependency graph. It automates the detection of directly modified crates, affected library crates, and affected binary crates, enabling targeted builds, tests, or deployments. This action helps streamline workflows by avoiding unnecessary processing of unaffected packages and supports force-trigger mechanisms for workspace-wide updates.
April 20, 2026
rust-affected
Version updated for https://github.com/RobertRautenbach/rust-affected to version v4.0.1.
This action is used across all versions by ? repositories. Action Type This is a Docker action.
Go to the GitHub Marketplace to find the latest changes.
Action Summary The rust-affected GitHub Action analyzes a Rust workspace to determine which packages are impacted by changes to specific files, leveraging the Cargo dependency graph. It automates the identification of directly modified crates, affected library and binary members, and whether a full workspace rebuild is needed due to specific trigger files. This action helps optimize workflows by narrowing the scope of tasks, such as testing or deployment, to only the impacted components in large Rust projects.
April 12, 2026
rust-affected
Version updated for https://github.com/RobertRautenbach/rust-affected to version v4.0.0.
This action is used across all versions by ? repositories. Action Type This is a Docker action.
Go to the GitHub Marketplace to find the latest changes.
Action Summary The rust-affected GitHub Action identifies which packages in a Rust workspace are impacted by file changes, leveraging the Cargo dependency graph. It automates the detection of directly changed crates, affected library and binary members, and provides an option to force the entire workspace as affected based on specific file modifications. This tool streamlines workflows by enabling targeted testing, builds, or deployments, reducing unnecessary processing and improving efficiency.