Conversation
Minor version bump ahead of release: workspace.package version, the sc-composer/sc-sha/sc-composer-beads path-dependency version pins, and the PyPI (sc-compose-py, sc-sha-python, sc-composer-beads-python) pyproject versions moved from 1.5.0 to 1.6.0 in lockstep. README version references synced. Cargo.lock regenerated via cargo update -p sc-composer -p sc-composer-beads -p sc-compose -p sc-sha --workspace. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The checked-in fixture Cargo.lock pins patch.unused entries to the workspace version; regenerate via cargo metadata to match the 1.6.0 bump. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…hecks cargo package -p sc-compose --locked fails at preflight time because sc-composer-beads (a new intermediate crate, publish_order 3) has not been published yet when preflight runs, so cargo's isolated verification build cannot resolve it via the crates.io index even though the manifest already declares the correct publish order ahead of sc-compose. --no-verify skips only that isolated rebuild; the real cargo publish step still verifies fully, in order, against the registry state at actual publish time.
…-blocking The prior --no-verify fix didn't work: cargo package must rewrite path+version dependencies to registry-resolvable versions during its manifest-prepare phase, before any verification build runs, so --no-verify never reaches the actual failure point. Verified locally that cargo package -p sc-compose --locked still fails identically with --no-verify present. Replace it with a targeted check: when cargo package fails specifically because a manifest-declared sibling crate (e.g. sc-composer-beads, not yet published on its first release) can't be resolved via the registry index, treat that as non-blocking and continue. Any other cargo package failure still hard-fails the step. The real cargo publish step runs for real, in manifest publish_order, so the sibling will already be live by the time sc-compose is actually published.
release: prepare 1.6.0
site: announce sc-compose v1.6.0
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
2 participants
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.
No description provided.