Skip to content

fix: release commit fails pre-push validate: migrations.test asserts at least one pending changeset #641

Closed

Description

@mvilacad

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

  1. added
    bugSomething isn't working
    area:teststest infra, flakes, CI
    in progressSomeone is working on it (see the linked draft PR)
    on Oct 25, 2026
  2. self-assigned this
    on Oct 25, 2026
  3. mvilacad commented on Oct 25, 2026

    @mvilacad
    ContributorAuthor

    Working on this in #642 (draft). Branch fix/641-fix-release-commit-fails-pre-push. Regression test first, then the fix.

  4. removed
    in progressSomeone is working on it (see the linked draft PR)
    on Oct 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area:teststest infra, flakes, CIbugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions