Repository navigation
Dependency count and bundle size increases are time-based, but should compare to nearest applicable version #3333
Description
Describe the bug
We believe the dependency count and bundle size warnings are based off release timing, leading to comical comparisons when a team releases bug fixes with backports :)
For instance here, we released a Storybook 11 alpha alongside 3 security backports for 8, 9 and 10. Storybook 11.0 a6 is compared to Storybook 9 but comparing to 11.0 a5 would make more sense.
Here Storybook 9 is compared to Storybook 8, even though the storybook 8 package was an empty shell back in the day.
Additional context
I think comparing to the previous semantic release would fix that. A X.0.0 major could compare to the previous stable release, but patch and minor releases would naturally compare to the code in their branch if doing based on semver.
Activity