Resolve release dependencies exclusively from crates.io - #186
Merged
Conversation
Merged
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.
Fission CI and published consumers now resolve the same external dependency graph. This removes the workspace-wide Winit and Android Activity patches, removes vendored Vello path resolution from publishable crates, and requires the newly published
fission-winit 0.30.13-fission.3containing the mobile and Web IME APIs used by Fission 0.14.0.\n\nA new CI boundary check rejects future[patch]/[replace]sections and external Git orthird_partypath dependencies in publishable manifests. The lockfile confirms Android Activity, the Fission Vello fork, and the Fission Winit fork all resolve from crates.io. This makes the existing Web, Android, iOS, and CLI jobs exercise the same external artifacts downstream users receive.