Skip to content

Upgrade up-rust to 0.9.0#45

Merged
PLeVasseur merged 1 commit into
eclipse-uprotocol:mainfrom
PLeVasseur:chore/upgrade-up-rust-0.9.0
Feb 6, 2026
Merged

Upgrade up-rust to 0.9.0#45
PLeVasseur merged 1 commit into
eclipse-uprotocol:mainfrom
PLeVasseur:chore/upgrade-up-rust-0.9.0

Conversation

@PLeVasseur

Copy link
Copy Markdown
Contributor

Summary

  • Upgrade [workspace.dependencies].up-rust from 0.5.0 to crates.io 0.9.0.
  • Align workspace rust-version from 1.76 to 1.82 because up-rust 0.9.0 declares rust_version = 1.82 on crates.io.
  • No code-level compatibility adaptations were required for listener/filter URI validation, payload extraction strictness, or communication API usage; existing code/tests compiled and ran successfully.

Crates.io Target Confirmation

  • crates.io API endpoint https://crates.io/api/v1/crates/up-rust reports:
    • max_version = 0.9.0
    • max_stable_version = 0.9.0
    • yanked = false

Lockfile Update

  • Ran: cargo update -p up-rust --precise 0.9.0
  • Local lockfile resolves up-rust 0.9.0 after update.
  • Cargo.lock is intentionally gitignored in this library workspace, so no lockfile diff is included in this PR.

Validation

Commands run from repo root:

source build/envsetup.sh highest
cargo check --all-targets
cargo clippy --all-targets -- -W warnings -D warnings
cargo test -- --test-threads 1

Outcomes:

  • cargo check --all-targets: pass
  • cargo clippy --all-targets -- -W warnings -D warnings: pass
  • cargo test -- --test-threads 1: first rerun cycle saw the known publisher_subscriber flaky one-message miss (86 sent / 85 received), then reran full serial suite once per project guidance and it passed.

@PLeVasseur
PLeVasseur merged commit 278ab26 into eclipse-uprotocol:main Feb 6, 2026
10 checks passed
@PLeVasseur
PLeVasseur deleted the chore/upgrade-up-rust-0.9.0 branch February 6, 2026 23:42
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.

1 participant