Fix isolated SwarmForge LSD packaging - #22
Merged
Conversation
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.
Follow-up from the fail-closed SwarmForge crates.io release.\n\nThe per-package dry-run caught that swarmforge-lsd relied on workspace feature unification for the SHA-1 backend. This change gives LSD an explicit default/ring feature contract, propagates the selected engine backend, and adds an audited --execute --resume mode with crates.io rate-limit handling.\n\nSeven earlier dependency packages are already immutable on crates.io; this correction affects only the still-unpublished LSD/engine artifacts. Local gates passed: isolated LSD cargo package and dry-run, LSD tests with default and ring backends, full workspace check/test/clippy -D warnings, formatting, shell syntax, and fail-closed publisher guard tests.