Resolve Cargo Publish Issues

[jio-gl]

Expected Behavior

Actual Behavior

in CI cargo publish gives Error: Error: Missing dependency 'sbtc-core' version field.

Docs: https://github.com/marketplace/actions/publish-crates

Action Code: https://github.com/katyo/publish-crates/blob/2fcfbf70241f794be7050d083dccec4edc27d754/src/package.ts#L36

Steps to Reproduce

Screenshots or Videos

[jio-gl]

Exploring some solutions in the Branch, the cargo publish is working locally for sbtc-core and sbtc-cli, but the Github Action is still throwing an error about dependency sbtc-core version missing:

Error: Error: Missing dependency 'sbtc-core' version field

The GH Action mentions these checks:

• Reads manifests to get info about crates and dependencies
• Checks versions of external dependencies to be exists in registry
• Checks matching paths and versions of internal dependencies
• Checks that no changes happened since published release when version of internal dependency is not changed

[jio-gl]

I think it can be solved by leaving the path field and removing the version field for dev deps that are part of the workspace. We have to make sure that the workspace deps are dev-dependencies:

https://github.com/katyo/publish-crates/blob/2fcfbf70241f794be7050d083dccec4edc27d754/src/package.ts#L120C17-L128C22

} else if (
                    // throw an error if there is no path or version on dev-dependencies
                    kind === 'dev' &&
                    no_version &&
                    !dependency.path
                ) {
                    throw new Error(
                        `Missing dependency '${name}' version field`
                    )

[jio-gl]

Use cargo check --workspace to parse and find workspace Cargo.toml problems.