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
cargo 1.83.0 has introduced a new behavior that colludes with how kraken publishes rust packages: up until 1.82, changing the version incargo.toml did not result in changes in Cargo.lock, but now it does; consequently causing the cargo publish command called by kraken to fail with errors regarding changes to lockfiles.
One mitigation I have found is to set cargo_publish_task.locked = False for cargo projects with single packages, but this approach also fails if there is more than one package that will be published (ie workspaces).
The text was updated successfully, but these errors were encountered:
cargo 1.83.0 has introduced a new behavior that colludes with how kraken publishes rust packages: up until 1.82, changing the version in
cargo.toml
did not result in changes inCargo.lock
, but now it does; consequently causing thecargo publish
command called by kraken to fail with errors regarding changes to lockfiles.One mitigation I have found is to set
cargo_publish_task.locked = False
for cargo projects with single packages, but this approach also fails if there is more than one package that will be published (ie workspaces).The text was updated successfully, but these errors were encountered: