Conversation
`ps-blitz-shell` moved to winit beta 3 on the 0.4 line, so a consumer whose
lockfile still pins beta 2 fails to *resolve* rather than to compile:
error: failed to select a version for `winit`
... required by package `ps-blitz-shell`
previously selected package `winit v0.31.0-beta.2`
... of package `tauri-runtime-blitz`
The floor here still said beta 2, which admits beta 3 but does not ask for it,
so nothing pulled a stale lock forward and the failure surfaced downstream in
the application rather than here. Asking for beta 3 is what makes
`cargo update` do it.
Beta 3 satisfies the published 0.4.2 engine as well, so this lands on its own.
This was referenced Sep 6, 2026
`ps-blitz-shell` on the 0.4 line requires winit beta 3, and the floor here said beta 2 -- which admits beta 3 without asking for it, so nothing pulled a stale lock forward and the failure surfaced downstream as `failed to select a version for winit`, naming winit and nothing about blitz. 0.3.2 is already on crates.io, and the publish workflow skips a version it finds there, so without the bump this lands and reaches nobody.
pathscale
changed the title
Owner
Author
|
Closing: the requirement was never wrong.
What actually failed downstream was a lockfile, not a requirement:
|
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.
ps-blitz-shellon the 0.4 line requireswinit ^0.31.0-beta.3. The floor here said beta 2, which admits beta 3 without asking for it, so a consumer with an older lockfile fails to resolve rather than to compile, and the error names winit rather than anything about blitz.Found while building AgencyZero against ps-blitz pathscale/ps-blitz#86; the build could not resolve until the lock moved forward.
Also releases 0.3.3. 0.3.2 is already on crates.io and the publish workflow skips a version it finds there, so without the bump this merges and reaches no consumer. Raised in review.
cargo check --all-featuresis clean. Beta 3 also satisfies the published 0.4.2 engine, so this does not wait on #86.