Update support for Rust inter-workspace dependencies

[johncarmack1984]

Motivation

Covector fails when processing Cargo.toml files that use workspace dependencies ({ workspace = true }) or path-only dependencies ({ path = "../pkg" }). These are valid Cargo dependency patterns, but covector throws an error because it expects all object-style dependencies to have an explicit version field.

This blocks monorepos that use Cargo's workspace dependency inheritance feature, which is the recommended pattern for managing versions across Rust workspaces.

Approach

Modified getPackageFileVersion in packages/files/src/index.ts to handle two additional Cargo dependency patterns:

1. Workspace dependencies ({ workspace = true }) - Version is inherited from the workspace root's [workspace.dependencies] section
2. Path-only dependencies ({ path = "../pkg" }) - Used for local development without publishing

For both patterns, the function now returns an empty string instead of throwing an error, allowing covector to continue processing.

Alternate Designs

Could have attempted to resolve the actual version from the workspace root for workspace = true dependencies. However, this would require additional file reads and workspace resolution logic. Returning an empty string is simpler and sufficient for covector's dependency tracking purposes.

Possible Drawbacks or Risks

• Dependencies using these patterns won't have their versions tracked/bumped by covector. This is acceptable since:
  • Workspace deps inherit their version from the workspace root (which covector can bump separately)
  • Path-only deps are typically dev/test dependencies not intended for publishing

TODOs and Open Questions

• Should covector attempt to resolve workspace dependency versions from the workspace root? Current approach treats them as unversioned.

Learning

• https://doc.rust-lang.org/cargo/reference/workspaces.html#the-workspace-section - Documentation on { workspace = true } pattern
• https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#specifying-path-dependencies - Documentation on path dependencies

Screenshots

see pasted terminal output below:

Before:

pkg-a has a dependency on serde, and serde does not have a version number. This cannot be published. Please pin it to a MAJOR.MINOR.PATCH reference.

After:

[info] apply changes ::  pkg-a planned to be bumped from 0.1.0 to 0.1.1

[github-actions]

Package Changes Through c0ce23e

No changes.

Add a change file through the GitHub UI by following this link.

---

Read about change files or the docs at github.com/jbolda/covector

[jbolda]

I want to make sure I understand the context here. Are you defining and publishing/changelog multiple crates as part monorepo where some/all have their version actually defined in the Cargo.toml at the root? Or is it just if any deps don't have a version number?

The intent of looking for the version number of a dep is that we bump it if it is declared as a dep and exists in the deps specified in Cargo.toml.

[johncarmack1984]

Wrapping a loose end I've felt bad about: your question in February landed right as I was leaving Flight Science. Then I lost write access to the fltsci fork this branch lives on, so I can't update or rebase it. Three options: I recreate this from my own fork and actually answer your question this time, you take the diff wholesale, or we close it. Whatever's least work for you. Sorry for the silence :)

[johncarmack1984]

Recreated as #397, rebuilt on current main with the February question answered in the description. Closing this one in its favor.