fix(release): install libfuse in the publish path, not just in CI - #15
Merged
Conversation
forensic-mount 0.6.1 failed to publish. The release PR was green and merged, so
the failure landed after the gate, inside release-plz:
failed to publish forensic-mount
failed to run custom build command for `fuser v0.16.0`
failed to verify package tarball
`cargo publish` verifies by building the packaged tarball, and that build links
libfuse through fuser exactly as the CI build jobs do. ci.yml has installed
libfuse3-dev + pkg-config since the fuser dependency landed — four jobs carry
the step, with a comment at the top of the file explaining why. release-plz.yml
never got it.
So CI proved the code builds and the publish path could not build it. The gap
was invisible until a release actually ran, because nothing else in the repo
exercises `cargo publish`.
Both jobs get the step: release verifies the tarball, and release-pr runs
`cargo package` while walking history to find the last published content.
bitlocker-forensic depends on fuser with the same shape and the same missing
step; it is fixed in its own PR rather than folded in here.
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.
forensic-mount 0.6.1 failed to publish. The release PR was green and merged, so
the failure landed after the gate, inside release-plz:
cargo publishverifies by building the packaged tarball, and that build linkslibfuse through fuser exactly as the CI build jobs do. ci.yml has installed
libfuse3-dev + pkg-config since the fuser dependency landed — four jobs carry
the step, with a comment at the top of the file explaining why. release-plz.yml
never got it.
So CI proved the code builds and the publish path could not build it. The gap
was invisible until a release actually ran, because nothing else in the repo
exercises
cargo publish.Both jobs get the step: release verifies the tarball, and release-pr runs
cargo packagewhile walking history to find the last published content.bitlocker-forensic depends on fuser with the same shape and the same missing
step; it is fixed in its own PR rather than folded in here.