Repository navigation
Publish izumo, not the crate it was renamed from - #58
Merged
Merged
Conversation
added 2 commits
September 23, 2026 18:55
The workflow still watched crates/tauri-runtime-blitz/Cargo.toml, asked crates.io about tauri-runtime-blitz and ran cargo publish -p tauri-runtime-blitz. The merge of the rename ran it, cargo found no such package, and izumo 0.4.1 was never published.
The repository moved to pathscale/izumo, and two log prefixes and the rebuild hint in the diagnostics error still named tauri-runtime-blitz.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The merge of #56 did not publish izumo.
publish.ymlstill watchedcrates/tauri-runtime-blitz/Cargo.tomland rancargo publish -p tauri-runtime-blitz, and cargo found no such package. Nothing is on crates.io underizumoyet.publish.yml: watchescrates/izumo/Cargo.toml, checks crates.io forizumo, and publishes-p izumo. Merging this triggers the workflow itself, so 0.4.1 publishes on merge; no version bump is needed because 0.4.1 was never published.pathscale/izumo:homepage/repository, two log prefixes, and the rebuild hint in the diagnostics error now say izumo.Checked locally:
cargo fmt --check, clippy--all-targets --all-features -D warnings, andcargo publish -p izumo --dry-run(packages, verifies and stops at upload).