Breaking Changes
- Batch size semantics changed:
0now means "disabled" instead of "unlimited"0= disabled (skip this batch type entirely — no API calls made)-1= unlimited (search all available items, weights ignored)N > 0= limited (search up to N items, distributed by weight)- Migration: Change
missing_batch_size: 0tomissing_batch_size: -1for unlimited behavior - If you previously used
missing_batch_size: 0for unlimited, update tomissing_batch_size: -1
Added
- Support for disabled batch types (
missing_batch_size: 0orupgrade_batch_size: 0) - Support for unlimited batch types (
missing_batch_size: -1orupgrade_batch_size: -1) - Per-batch-type disabled logging: separate log messages when only one batch type is disabled
- Startup log now displays "Disabled" or "Unlimited" for batch sizes (instead of
0or-1)
Changed
- Config validation now accepts
-1formissing_batch_sizeandupgrade_batch_size - Config validation rejects values below
-1for batch size settings (e.g.-2is invalid) - When set to unlimited, batch size weights are not applied (each instance gets all items)
retry_interval_daysstill applies in unlimited mode