Skip to content

chore(rust): raise rust-version to 1.88, what the dependencies already need - #17

Merged
neurolabusc merged 1 commit into
mainfrom
chore/rust-version-1.88
Oct 14, 2026
Merged

neurolabusc merged 1 commit into
mainfrom
chore/rust-version-1.88

Conversation

@cdrake

@cdrake cdrake commented Oct 13, 2026

Copy link
Copy Markdown
Contributor

Why

src-tauri/Cargo.toml says rust-version = "1.85", but BIDSvue hasn't built on 1.85 for a while. On 1.85, cargo check stops before compiling anything:

error: rustc 1.85.1 is not supported by the following packages:
  darling@0.23.0 requires rustc 1.88.0
  icu_collections@2.2.0 requires rustc 1.86
  ...

The highest rust-version among the locked dependencies is 1.88: darling 0.23, time 0.3.47, plist 1.9 and serde_with 3.19. Every CI job installs the latest stable Rust, so nothing noticed the gap.

Change

rust-version = "1.88", with the comment updated to say where the number comes from. Cargo.lock is unchanged. The datalad-rs submodule keeps its own pin (1.85); changing it is a separate change in that repo.

Note: AtomicU64::try_update is still unstable in 1.88, so #16's compare-exchange loop remains the right fix for the fetch_update deprecation. The two PRs are independent.

Test

  • cargo +1.88 check --workspace --all-targets: clean, no warnings.
  • cargo +1.87 check: refused with bidsvue requires rustc 1.88, as intended.

🤖 Generated with Claude Code

…y need

rust-version said 1.85, but the locked dependencies need 1.88 (darling
0.23, time 0.3.47, plist 1.9, serde_with 3.19), so 1.85 could not build
BIDSvue anyway. CI only builds on latest stable, so nothing caught it.
`cargo +1.88 check --workspace --all-targets` is clean. The datalad-rs
submodule keeps its own pin.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@neurolabusc
neurolabusc merged commit 31d75ed into main Oct 14, 2026
3 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants