feat: Add --ignore-version option to mason add to bypass brick.yaml version checks

[shinriyo]

Description

Currently, when using mason add to install a brick, the command fails if the brick's brick.yaml includes a mason environment constraint that does not match the current mason version.

Example:

The current mason version is 0.1.1.
Because a_page requires mason version >=0.1.0-dev.26 <0.1.0, version solving failed.

This is a common issue for older bricks created before Mason 0.1.0 was released.

I propose adding an --ignore-version (or --force) flag to mason add that bypasses this version check and logs a warning instead, allowing the user to proceed.

---

Requirements

• Add --ignore-version (or --force) flag to mason add
• When this flag is used, skip the mason version constraint validation from brick.yaml
• Print a warning message indicating version incompatibility
• Keep current behavior strict by default

---

Additional Context

Many community bricks on GitHub are locked to old dev versions like 0.1.0-dev.47, making them unusable on the current stable version (0.1.1).

This enhancement would let users install older bricks without modifying their brick.yaml manually.

Example usage:

mason add --global a_page --ignore-version

[felangel]

Thanks for opening an issue!

Why not just update the brick.yaml for the relevant bricks? Are there specific bricks in mind that you can’t use?

[shinriyo]

@felangel

Thanks for your reply!

I understand that updating the brick.yaml is one solution, and I’ve actually done that many times across various bricks.
However, creating pull requests to different branches of various brick authors each time has become quite tiring.
That’s why I thought adding a --ignore-version option could help streamline the experience, especially when trying out community-maintained bricks that haven’t been updated recently.