fail if compiled size of breakout example in release increase by more than 0.5%

[mockersf]

Objective

• Fail in CI when compiled size increase too much

Solution

• When merging, build on base, build on head, compare the two sizes
• Fail when the new size is more than 100.5 * old size
• Current size on macOS is 81MB, this would allow a size increase of 417kB

[IceSentry]

Is there a way to allow an increased size if we know we'll do something that increases it? Or is the plan in these cases that we'd merge a PR that increases the limit first

[mockersf]

Is there a way to allow an increased size if we know we'll do something that increases it? Or is the plan in these cases that we'd merge a PR that increases the limit first

Yup!
The maintainer trying to merge the PR can make this job not required in the branch protection rules so that it's not blocking a merge 😄

Not the best, but if the other maintainers agree I think it would be good enough to test drive this. if it happens too often, we could look into adding a label to ignore this check

[hymm]

should this just be a fixed size? having it be a percentage feels a bit off. i.e. if we're talking about a pr that embedded a 1MB asset if the current executable size is 200MB then this would be allowed. But I feel like we'd want to deny any 1MB increase in size.