Sync Cargo.lock

[themadprofessor]

Recently I created an AUR Git Package, and the AUR Guidelines recommend using cargo fetch --frozen for reproducible builds. Looks like something caused Cargo.lock and Cargo.toml to desync, which causes cargo fetch --frozen to fail.

Would it also be possible to tag releases on the main branch as soon as they are released? The AUR Git package bases its version of the last tag on main. When a new version is released and the main branch doesn't have the new tag, people mark the package as out-of-date, even though it contains the "latest" code.

[auyer]

Hmm interesting. I have to look into this.

The desync was probably my fault.

I am currently making the release based on a release branch instead of the main branch.
When developing locally, we point to the relative path for libprotonup, but when making a release, I need to publish the lib to crates.io first.

Reference commit in the release branch:
7daa68a

Changing it in main would make it annoying to anyone that wants to clone the repo and test things.

[auyer]

Yeah, I found what caused the desync.
I created the release in a single commit.
The build for protonup-rs happens right after libprotonup is published to crates.io.
But the lock file could not have the updated information, because they were not available yet when I created the commit.

Well, we have to find another way then.
I will merge this PR, but we can keep discussing this here or we can create an issue specific for this.

Also, thanks for taking this project to the AUR!
I wanted to create a bin repo, but haven't looked into it yet.