Skip to content

chore(release): duroxide 0.1.30 - #43

Merged
pinodeca merged 1 commit into
mainfrom
release/v0.1.30
Jul 29, 2026
Merged

chore(release): duroxide 0.1.30#43
pinodeca merged 1 commit into
mainfrom
release/v0.1.30

Conversation

@pinodeca

Copy link
Copy Markdown
Contributor

Summary

  • bump duroxide from 0.1.29 to 0.1.30
  • publish release notes for safer sub-orchestration IDs, collision handling, parent-link preservation across continue-as-new, and UUID generation
  • add the missing changelog entry for PR Preserve sub-orchestration parent link across ContinueAsNew #31
  • update the README latest-release link and summary
  • apply formatter and current-toolchain Clippy cleanups required by the release gate
  • make the heterogeneous session test account for at-least-once activity retries after transient ack failures

Validation

  • cargo fmt --all --check
  • cargo clippy --all-targets --all-features -- -D warnings
  • cargo nt --no-fail-fast: 1,117 passed
  • cargo nextest run --no-default-features --no-fail-fast: 1,114 passed
  • cargo test --doc: 46 passed, 74 ignored
  • test_multi_worker_heterogeneous_config: 10/10 repeated isolated passes
  • cargo package -p duroxide --locked --allow-dirty: passed
  • package/archive inspection: 263 clean entries
  • cargo publish -p duroxide --dry-run --locked --allow-dirty: passed

Dependency audit

cargo audit reports RUSTSEC-2023-0071 for rsa 0.9.10, an unused lockfile entry pulled through sqlx-mysql. cargo tree --all-features --target all -e all --invert rsa and the equivalent sqlx-mysql query show no reachable dependency edge. The audit passes when only this unreachable advisory is scoped out; no other advisories are reported.

@pinodeca
pinodeca merged commit cfe0b8c into main Jul 29, 2026
1 of 2 checks passed
@pinodeca
pinodeca deleted the release/v0.1.30 branch July 29, 2026 14:08
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