chore(release): --allow-dirty when publishing hyperdb-compile-check#103
Merged
StefanSteiner merged 1 commit intoJun 2, 2026
Merged
Conversation
hyperdb-compile-check is its own workspace with its own committed Cargo.lock (it's intentionally outside the root workspace). When the release publishes hyperdb-api to crates.io moments earlier, cargo re-resolves hyperdb-compile-check's lockfile against the live index during packaging, leaving hyperdb-compile-check/Cargo.lock modified in the working tree. `cargo publish` then aborts: error: 1 files in the working directory contain changes that were not yet committed into git: hyperdb-compile-check/Cargo.lock Add --allow-dirty to that one publish call. The root-workspace crates (hyperdb-mcp, -bootstrap, sea-query-hyperdb) don't need it — they share the root Cargo.lock that release-please already synced to 0.4.0, so it stays clean during their packaging. This was the last blocker: salesforce, core, and hyperdb-api are already published; this unblocks compile-check → derive → mcp → bootstrap → sea-query.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
hyperdb-compile-check is its own workspace with its own committed Cargo.lock (it's intentionally outside the root workspace). When the release publishes hyperdb-api to crates.io moments earlier, cargo re-resolves hyperdb-compile-check's lockfile against the live index during packaging, leaving hyperdb-compile-check/Cargo.lock modified in the working tree.
cargo publishthen aborts:error: 1 files in the working directory contain changes that were not
yet committed into git: hyperdb-compile-check/Cargo.lock
Add --allow-dirty to that one publish call. The root-workspace crates (hyperdb-mcp, -bootstrap, sea-query-hyperdb) don't need it — they share the root Cargo.lock that release-please already synced to 0.4.0, so it stays clean during their packaging.
This was the last blocker: salesforce, core, and hyperdb-api are already published; this unblocks compile-check → derive → mcp → bootstrap → sea-query.