šŸ„ Modular YAML limits increased: up to 35 files

Changelog Website
,
1

Weā€™ve increased the limits for modular bitrise.yml configurations to give you more flexibility in organising complex projects.

Hereā€™s precisely what changed:

  • Total files: up to 35 configuration files, including root bitrise.yml (previously capped at 20).
  • Includes per file: no limit (previously capped at 10), as long as the total number of files remains 35 or fewer.
  • Nesting depth: still limited to 5 levels maximum

:puzzle_piece: What problem this solves

If youā€™ve ever managed a large monorepo or maintained a complex set of workflows for different teams and platforms, you may have hit our previous configuration limits.

This often forced you to create larger, less reusable YAML files, compromising on a clean, component-based structure. You had to stop organising and start combining files to stay within the limits, making your configurations harder to maintain.

These new limits are designed to remove that barrier, allowing you to structure your YAML in a way that better reflects your projectā€™s architecture.

This means a single bitrise.yml could now theoretically include 34 other files (35 in total, including the root bitrise.yml) directly, or you could have a more deeply nested structure across multiple files, as long as the total count and depth are respected.

:gear: How it works

If you havenā€™t used the Modular YAML feature before, check the docs out here. The include functionality itself has not changed. You still use it to import Step Bundles, Workflows, or entire configurations from other YAML files. The only difference is the new limits - you can now have more modules.

:light_bulb: When to use Modular YAML

We published a detailed blog post on this topic. Check it out!

2

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.