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.
Vendor the
json-ld
crate dependency using a git submodule, to enable publish tocrates.io
.Progress for #136
Fixes #90
Includes #140, to get CI to work (Closes #140)
Cargo dependencies using git repo URLs cannot be used for publishing to
crates.io
(unless also including a registry version for publishing). We are depending on thejson-ld
crate with changes which are not yet published tocrates.io
. Without being able to depend on this two crates oncrates.io
, we must either fork and publish it tocrates.io
under a different name, or vendor it somehow. I wasn't able to getcargo vendor
to work, and I'm not sure if that can be used (source replacement) with publishing tocrates.io
anyway. Instead, the approach taken here is to modify the package to make it work inssi
's workspace. It seems to be working to use a git submodule rather than having to include the repos' source files directly. Thejson-ld
repos is forked and added to git submodules. The changes tojson-ld
are in the following PR, proposing to use a branchvendor
for our fork: https://github.com/spruceid/json-ld/pull/1cargo publish --dry-run
works