Previous amboso versions may have backwards incompatible changes at minor version level.
This could be addressed in 2.x by adding some logic to handle each breaking change in 1.x.
Handling for each cutoff
Just straight up not try working with some cutoffs and reject them with a "helpful" error message - :heavy_multiplication_x:
Report curated error messages for unstable versions in some cutoffs - :x:
Try altering passed arguments to ensure interoperability (provided there's no external changes to the environment) - :question:
Proposed cutoffs
Handling
Reasoning
<=1.4.2
:heavy_multiplication_x:
amboso_fn.sh does not contain AMBOSO_API_LVL="X.Y.Z"
Previous
ambosoversions may have backwards incompatible changes at minor version level. This could be addressed in2.xby adding some logic to handle each breaking change in1.x.Handling for each cutoff
Try altering passed arguments to ensure interoperability (provided there's no external changes to the environment) - :question:
<=1.4.2amboso_fn.shdoes not containAMBOSO_API_LVL="X.Y.Z">1.4.2, <1.6.6>=1.6.6, <=1.7.4stego.lockformat>1.7.4, <= 1.9.6>1.9.6, < 2.xinvil<0.2.x