Repository navigation
chore: write minimumReleaseAge as 3d and exclude bun-types - #188
Conversation
@types/bun was already excluded, but its bun-types dependency was not, so a fresh Bun release could not be bumped inside the three-day window without a one-off flag. Bun 1.4.4 accepts duration strings, so 3d replaces 259200.
There was a problem hiding this comment.
bompus has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 30 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@coderabbitai full review |
|
Bun 1.4.4 accepts duration strings for
minimumReleaseAge, sobunfig.tomlnow says"3d"instead of259200(same three days). It also addsbun-typestominimumReleaseAgeExcludesnext to@types/bun. Without that entry, bumping@types/bunto a fresh Bun release failed because itsbun-typesdependency was still inside the three-day window, and each bump needed a one-off command-line exclude.The duration form needs Bun 1.4.4 or later; Bun 1.4.3 and earlier read only a number.
bun run checkpasses locally on Bun 1.4.4.Summary by cubic
Updates
bunfig.tomlso fresh Bun releases can be bumped without one-off workarounds.minimumReleaseAgenow uses"3d"instead of259200(same three days), andbun-typesjoins@types/buninminimumReleaseAgeExcludesso a new@types/bunbump isn't blocked by its ownbun-typesdependency staying inside the wait window.The
"3d"duration form requires Bun 1.4.4 or later.Written for commit e30bb2c. Summary will update on new commits.