Skip to content

bump version #55

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.

Sign up for GitHub

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

Closed
The64thRealm wants to merge 2 commits into from
+2 −2
Closed

bump version #55

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
19ed91d
bump version
The64thRealm Aug 14, 2026
7dd7ed9
update cargo lock
The64thRealm Aug 14, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Cargo.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[package]
name = "wavedash"
version = "0.1.92"
version = "0.1.93"
Comment thread
devin-ai-integration[bot] marked this conversation as resolved.

@claude claude Bot Aug 14, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cargo.lock still records the old version — the wavedash entry at Cargo.lock:3079 is version = "0.1.92", so with this bump the committed lockfile no longer matches the manifest.

Nothing in CI passes --locked, so cargo clippy / cargo test will silently rewrite the lock and still pass, but anyone building the 0.1.93 tag with a frozen lockfile hits it: cargo build --locked (or --offline, or cargo install --locked) fails with error: the lock file .../Cargo.lock needs to be updated but --locked was passed to prevent this. It also means the released tag's lockfile does not record the version actually shipped. The previous release (beade68) kept the two in sync, so this is a regression in that convention.

Fix by regenerating the lock alongside the manifest bump (cargo update -p wavedash --precise 0.1.93, or just cargo check) and committing Cargo.lock.

edition = "2021"
authors = ["Wavedash Team"]
description = "Cross-platform CLI tool for uploading game projects to wavedash.com"
Expand Down
Loading