chore(release): bump workspace version to 0.1.12
Release / prepare draft release (push) Successful in 5s
Release / build (aarch64-apple-darwin) (push) Failing after 1s
Release / build (x86_64-apple-darwin) (push) Failing after 2s
Release / build (x86_64-pc-windows-msvc) (push) Canceled after 0s
Release / publish release (push) Canceled after 0s
Release / build (aarch64-unknown-linux-gnu) (push) Successful in 18m14s
Release / build (x86_64-unknown-linux-gnu) (push) Successful in 17m20s
Release / prepare draft release (push) Successful in 5s
Release / build (aarch64-apple-darwin) (push) Failing after 1s
Release / build (x86_64-apple-darwin) (push) Failing after 2s
Release / build (x86_64-pc-windows-msvc) (push) Canceled after 0s
Release / publish release (push) Canceled after 0s
Release / build (aarch64-unknown-linux-gnu) (push) Successful in 18m14s
Release / build (x86_64-unknown-linux-gnu) (push) Successful in 17m20s
Every crate inherits `workspace.package.version`, so the single edit plus the refreshed lockfile carries the release. The `v0.1.12` tag is what triggers the build; release.yml gates the tag against this value, and `cargo metadata --locked` passes so the build's `--locked` will too. This is the first release cut on Gitea Actions. v0.1.6 through v0.1.9 were all cancelled for want of a runner whose label matched anything, so nothing has ever published from the new forge — `releases/latest` still 404s, which is exactly why `kigi update` finds nothing today. Ships the link migration in the previous commit, so the installers and self-updater published here point at Gitea instead of a GitHub repo that no longer serves them. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
1 parent
9fb82291b2
commit
479fb8cbbd
2 files changed
+63
-63
No files matched your search
+1
-1
@@ -76,7 +76,7 @@ members = [
|
||||
]
|
||||
|
||||
[workspace.package]
|
||||
version = "0.1.11"
|
||||
version = "0.1.12"
|
||||
edition = "2024"
|
||||
license = "Apache-2.0"
|
||||
|
||||
|
||||
Reference in new issue
Block a user