Skip to content

release-please bumps break skene's explicit version lockstep (nix --locked fails on main) #766

Description

@forkwright

Finding

PR #759 made skene's manifest standalone-parseable (explicit version/edition/license, per the dependabot-isolation fix). Release-please then bumped the root lock's skene entry for 0.4.4 without touching skene's explicit version, and main's nix run failed at cargo check --release --locked (cannot update the lock file ... --locked). Fixed once in #764 by hand-bumping skene to 0.4.4.

Recurrence

Every future release-please bump re-breaks this: the lock entry moves, the explicit version doesn't. PR gates never exercise --locked, so only main's nix run catches it — post-merge, not pre-merge.

Candidate fixes

  • release-please extra-files entry for crates/theatron/core/Cargo.toml (keep the explicit version in lockstep automatically), or
  • a --locked metadata check on release PRs (catch pre-merge).

Surfaced during the 2026-09-03 fleet sweep; context in #759/#764.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions