Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cargo_publish tasks fail with cargo 1.83.0 #293

Open
ulucs opened this issue Jan 3, 2025 · 0 comments
Open

cargo_publish tasks fail with cargo 1.83.0 #293

ulucs opened this issue Jan 3, 2025 · 0 comments

Comments

@ulucs
Copy link
Contributor

ulucs commented Jan 3, 2025

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

1 participant