You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix: release commit fails pre-push validate: migrations.test asserts at least one pending changeset #641
bun run release versions the package, which consumes every changeset. The pre-push validate then runs migrations.test.ts "every pending changeset passes the policy", which asserts files.length > 0, fails on the release commit, and blocks the atomic push. Seen in the 4.6.0 release: all gates passed, the push was rejected, and nothing reached origin. Fix: an empty .changeset/ is valid (the policy applies to each changeset present).
Activity
mvilacad commentedon Oct 25, 2026
Working on this in #642 (draft). Branch
fix/641-fix-release-commit-fails-pre-push. Regression test first, then the fix.fix: changeset policy test accepts an empty changeset dir (#641)
fix: fix: release commit fails pre-push validate: migrations.test ass…