v6.13.0

What's Changed

• Remove linter warnings in wasm and release mode by @temeddix in #361
• Add doc comments for DartSignal and RustSignal fields by @temeddix in #362
• Remove all code that can possibly panic by @temeddix in #363
• Consider base href on the web by @temeddix in #364
• Upgrade tokio_with_wasm to 0.5.3 by @temeddix in #365
• Make Rinf commands work in offline environments by @temeddix in #369
• 32-bit message ID by @temeddix in #370
• Optional multi-threaded runtime by @temeddix in #372
• Use the true current-thread tokio runtime by default by @temeddix in #373
• Update docs by @temeddix in #375
• Reduce memory copy on Dart signal by @temeddix in #374
• Treat backtrace as an optional feature by @temeddix in #376
• Remove old guides by @temeddix in #377
• Make the return type of the main empty by @temeddix in #379
• Make get_dart_signal_receiver return Result by @temeddix in #380
• Return RinfError on errors by @temeddix in #381
• Allow dot in the proto package name by @temeddix in #387
• Provide finalizeRust to shut down the tokio runtime by @temeddix in #390

Full Changelog: v6.12.1...v6.13.0

• The get_dart_signal_receiver function now returns Result. You need to use unwrap or ? to retrieve Dart signal receivers from the generated message structs.
• You now need to manually provide the generated assignRustSignal to the initializeRust function, which can be imported using import 'package:rinf/rinf.dart'; in Dart.
• The tokio runtime will now default to being single-threaded. To use a multi-threaded tokio runtime, enable the new rt-multi-thread crate feature.
• By default, backtraces will be hidden in the CLI, with only the error message being printed. To display the Rust backtrace, enable the new backtrace crate feature.