bootandy/archived-dust
1
0
Fork 0
mirror of https://github.com/bootandy/dust.git synced 2026-06-08 11:29:05 +03:00
Code Issues 21 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #418] Lock file for v1.1.0 not up to date #179

New Issue
Closed
opened 2026-06-08 11:26:01 +03:00 by zhus · 3 comments
zhus commented 2026-06-08 11:26:01 +03:00
Owner
Copy Link
Copy Source

Originally created by @alerque on GitHub (Jul 17, 2024).
Original GitHub issue: https://github.com/bootandy/dust/issues/418

I'm trying to update distro packages (Arch Linux) which build with --frozen and the lock file for the release is not up to date with the manifest, so it won't build. Please make sure to update the lock file in conjunction with releases so they can be built in a reproducible manner. Thanks.

Originally created by @alerque on GitHub (Jul 17, 2024). Original GitHub issue: https://github.com/bootandy/dust/issues/418 I'm trying to update distro packages (Arch Linux) which build with `--frozen` and the lock file for the release is not up to date with the manifest, so it won't build. Please make sure to update the lock file in conjunction with releases so they can be built in a reproducible manner. Thanks.
zhus closed this issue 2026-06-08 11:26:01 +03:00
zhus commented 2026-06-08 11:26:01 +03:00
Author
Owner
Copy Link
Copy Source

@alerque commented on GitHub (Jul 17, 2024):

The culprit seems to be having bumped the version of this crate in Cargo.toml but not run cargo build to update the lock file to match. When cutting releases it is important to update both places!

<!-- gh-comment-id:2232745793 --> @alerque commented on GitHub (Jul 17, 2024): The culprit seems to be having bumped the version of *this* crate in Cargo.toml but not run `cargo build` to update the lock file to match. When cutting releases it is important to update both places!
zhus commented 2026-06-08 11:26:01 +03:00
Author
Owner
Copy Link
Copy Source

@bootandy commented on GitHub (Jul 17, 2024):

Sorry my bad. I have a performance bug to fix in v1.1.0 so I'll release v1.1.1 shortly.

<!-- gh-comment-id:2233906702 --> @bootandy commented on GitHub (Jul 17, 2024): Sorry my bad. I have a performance bug to fix in v1.1.0 so I'll release v1.1.1 shortly.
zhus commented 2026-06-08 11:26:01 +03:00
Author
Owner
Copy Link
Copy Source

@bootandy commented on GitHub (Jul 17, 2024):

pushing a new version now

Updated release notes - so hopefully won't make this mistake again:
https://github.com/bootandy/dust/commit/dbd18f90e7b184d12f14533e76e5915dbe4a2051

<!-- gh-comment-id:2234000591 --> @bootandy commented on GitHub (Jul 17, 2024): pushing a new version now Updated release notes - so hopefully won't make this mistake again: https://github.com/bootandy/dust/commit/dbd18f90e7b184d12f14533e76e5915dbe4a2051
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
good first issue
help wanted
pull-request
Mirrored from GitHub Pull Request
 windows help wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
zhus (Sergey Zhukov)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: bootandy/archived-dust#179
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?