You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
after I pushed the v1.1.0 release tag, release-libs.yaml was triggered
we got the following errors for multiple crates:
Uploading codec_sv2 v1.2.1 (/home/runner/work/stratum/stratum/protocols/v2/codec-sv2)
error: failed to publish to registry at https://crates.io/
Caused by:
the remote server responded with an error (status 400 Bad Request): unknown or invalid license expression; see http://opensource.org/licenses for options, and http://spdx.org/licenses/ for their identifiers
Note: If you have a non-standard license that is not listed by SPDX, use the license-file field to specify the path to a file containing the text of the license.
See https://doc.rust-lang.org/cargo/reference/manifest.html#the-license-and-license-file-fields for more information.
MIT + Apache-2.0
^ `+` must not follow whitespace
Error: Process completed with exit code 101.
prior to #1193, all protocols crate manifests only had MIT (which I believe was wrong, btw)
and the workspace manifestss had MIT + Apache-2.0
on #1193 we moved the license field away from the workspace manifests, and the protocols crate manifests ended up with MIT + Apache-2.0
while this is the correct license, according to this, we should be using the following syntax:
[package]
# ...license = "MIT OR Apache-2.0"
there was even a discussion about it #1193 (comment) and we ended up making the wrong decision
so we need to fix this before finishing the v1.1.0 release
The text was updated successfully, but these errors were encountered:
after I pushed the
v1.1.0
release tag,release-libs.yaml
was triggeredwe got the following errors for multiple crates:
prior to #1193, all
protocols
crate manifests only hadMIT
(which I believe was wrong, btw)and the workspace manifestss had
MIT + Apache-2.0
on #1193 we moved the license field away from the workspace manifests, and the
protocols
crate manifests ended up withMIT + Apache-2.0
while this is the correct license, according to this, we should be using the following syntax:
there was even a discussion about it #1193 (comment) and we ended up making the wrong decision
so we need to fix this before finishing the
v1.1.0
releaseThe text was updated successfully, but these errors were encountered: