Jeet major version API drift affecting Stylus grid reproducibility

In team environments using Jeet for Stylus-based grid layouts, achieving consistent grid output across developer machines requires aligning the Jeet library version with the Stylus compiler. Jeet's grid is a compile-time feature resolved during Stylus preprocessing, meaning the column() and shift() mixin behavior is determined by the library version in effect at compile time.

However, Jeet's API has undergone changes across major releases, particularly in the signatures and default calculations of column() and shift(). This version sensitivity creates uncertainty when deciding whether to pin Jeet to an exact semver version, allow floating major updates, or adopt a compatible range, since each approach may produce divergent grid output in the compiled CSS.

• What is the minimal version-range strategy that preserves grid consistency across Stylus updates?
• How does Jeet's compile-time resolution affect transitive dependency version conflicts?
• Should teams adopt exact version pinning or semver ranges for repeatable grid behavior?