ci(release): clone soap-server outside repo to fix dirty-tree publish - #4
Merged
Conversation
The previous fix checked out soap-server into soap-server-dep INSIDE the
onvif-server working tree, which left an untracked directory that trips
`cargo publish`'s dirty-tree check ("files in the working directory contain
changes not yet committed"). Clone soap-server into ../soap-server (outside
the repo) instead — it satisfies the crossref path dep without dirtying
onvif's tree. soap-server is public now, so no token/symlink needed.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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 to #3. Checking out soap-server into
soap-server-depinside the repo left an untracked dir that tripscargo publish's dirty-tree check. Clone into../soap-server(outside the working tree) instead; soap-server is public so no token needed. Merging does not publish (fix/* branch); I'll dispatch release.yml after merge.