Custom Rules

To define project-specific upgrade rules, create or edit the .ruby-upgrade-toolkit/rules.yml file and run the rules command to validate and activate policies governing gem pins, swaps, private sources, and verification gates. This centralizes governance for consistent team upgrades.

Custom upgrade rules enforce project-specific policies for Ruby and Rails upgrades, ensuring consistent governance across teams. They manage gem pins, swaps, private sources, and verification gates to ensure safe upgrade paths by applying policy overrides through a shared rules-engine.

Yes, the rules feature validates your rules.yml structure against a rules schema. It supports defaults, conflict detection, and credential preflight checks to ensure safe upgrades before you activate any gem pins, swaps, or verification gates.

You can author, validate, show, add, remove, enable, disable, and explain gem pins and swaps using the rules command. This applies project-specific policies from your rules.yml file to ensure safe and governed Rails upgrade paths.

Yes, the feature relies on a shared rules-engine to apply policy overrides and ensure safe upgrade paths. The engine processes your rules.yml to manage gem pins, swaps, private sources, and verification gates across Ruby and Rails upgrades.

When conflicts occur in your custom upgrade rules, the validation process detects them during structure validation against the rules schema. It also performs credential preflight checks to prevent unsafe upgrades, ensuring your gem pins and swaps remain safe.