chore: release v0.2.8 (veilid 0.5.5)#32
Merged
Merged
Conversation
Upgrade to veilid 0.5.5: bump veilid-core (default + android) v0.5.4 -> v0.5.5 and save-dweb-backend v0.3.10 -> v0.3.11 (built against veilid 0.5.5). Package version -> 0.2.8. hickory-resolver pin and tripledoublev/iroh patch retained: veilid-tools v0.5.5 still pins hickory-resolver 0.25.2. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Summary
veilid-coregit tagv0.5.4→v0.5.5in both stanzas (default deps +cfg(target_os = "android")target).save-dweb-backendgit tagv0.3.10→v0.3.11(built against veilid 0.5.5; chore: upgrade to veilid 0.5.5 save-dweb-backend#40).0.2.7→0.2.8.hickory-resolver = "=0.25.2"and the 7tripledoublev/iroh[patch.crates-io]entries are unchanged —veilid-toolsv0.5.5 still pinshickory-resolver 0.25.2.Test plan
cargo build✅cargo nextest run -E 'test(basic_test) | test(test_health_endpoint) | test(test_upload_list_delete)'✅ — 3 passed.test_refresh_empty_grouppasses on 0.5.5 ✅. It surfaced as flaky during the full run (TryAgain: offline— Veilid network-attach timing); verified pre-existing: the same test is flaky on the 0.5.4 baseline (failed 3 tries, passed on the 4th). Not a 0.5.5 regression.Follow-up (separate)
test_refresh_empty_grouplacks the retry override its sibling refresh tests have in.config/nextest.toml; adding it there would stabilize CI. Out of scope for this dependency bump.Final step of the Veilid 0.5.5 cross-repo cascade (veilid-iroh-blobs v0.3.7 ✅ → save-dweb-backend v0.3.11 ✅ → save-rust v0.2.8).
🤖 Generated with Claude Code