Sourced from insta's releases.
1.42.0
Release Notes
- Text snapshots no longer contain
snapshot_type: text
in their metadata. For context, we originally added this in the prior release (1.41.0) to support binary snapshots, but some folks disliked the diff noise on any snapshot changes, and the maintainers' weighted votes favored reverting. I apologize that this will cause some additional churn for those who usedcargo test --force-update-snapshots
to update their snapshots to the 1.41 format; running this again with 1.42 will remove those metadata entries. To confirm: this doesn't affect whether snapshot tests pass or fail — the worst impact is some additional diffs in metadata. #690- Pending snapshots are no longer removed throughout the workspace by
cargo-insta
before running tests. Instead, running a test will overwrite or remove its own pending snapshot. To remove all pending snapshots, usecargo insta reject
or run tests with--unreferenced=delete
. #651insta::internals::SettingsBindDropGuard
(returned fromSettings::bind_to_scope
) no longer implementsSend
. This was incorrect and any tests relying on this behavior where not working properly. Fixes #694 in #695 by@jalil-salame
Install cargo-insta 1.42.0
Install prebuilt binaries via shell script
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/mitsuhiko/insta/releases/download/1.42.0/cargo-insta-installer.sh | sh
Install prebuilt binaries via powershell script
powershell -ExecutionPolicy ByPass -c "irm https://github.com/mitsuhiko/insta/releases/download/1.42.0/cargo-insta-installer.ps1 | iex"
Download cargo-insta 1.42.0
File Platform Checksum cargo-insta-aarch64-apple-darwin.tar.xz Apple Silicon macOS checksum cargo-insta-x86_64-apple-darwin.tar.xz Intel macOS checksum cargo-insta-x86_64-pc-windows-msvc.zip x64 Windows checksum cargo-insta-x86_64-unknown-linux-gnu.tar.xz x64 Linux checksum cargo-insta-x86_64-unknown-linux-musl.tar.xz x64 MUSL Linux checksum
Sourced from insta's changelog.
1.42.0
- Text snapshots no longer contain
snapshot_type: text
in their metadata. For context, we originally added this in the prior release (1.41.0) to support binary snapshots, but some folks disliked the diff noise on any snapshot changes, and the maintainers' weighted votes favored reverting. I apologize that this will cause some additional churn for those who usedcargo test --force-update-snapshots
to update their snapshots to the 1.41 format; running this again with 1.42 will remove those metadata entries. To confirm: this doesn't affect whether snapshot tests pass or fail — the worst impact is some additional diffs in metadata. #690- Pending snapshots are no longer removed throughout the workspace by
cargo-insta
before running tests. Instead, running a test will overwrite or remove its own pending snapshot. To remove all pending snapshots, usecargo insta reject
or run tests with--unreferenced=delete
. #651insta::internals::SettingsBindDropGuard
(returned fromSettings::bind_to_scope
) no longer implementsSend
. This was incorrect and any tests relying on this behavior where not working properly. Fixes #694 in #695 by@jalil-salame
c20f566
Bump version to 1.42.0 (#703)aca7fe4
Update changelog for 1.42; add snapshot_kind
explanation
(#702)3f1e9a1
Fix clippy error & run --all-features
in CI (#701)f750c5b
Update dist
config (#700)60638c2
Defer to cargo metadata
to evaluate the workspace root (#660)1d9ddea
Don't clear unrelated pending snapshots (#651)966746a
Replace lazy_static
with once_cell
(#698)0caaaca
fix(settings): mark drop guard as !Send (#695)0283774
Don't add snapshot_kind: text
to snapshots (#690)f2783e5
Fix warning, make them errors in CI (#693)Sourced from moka's changelog.
Version 0.12.10
Changed
- Disable the
quanta
feature by default. (#482[gh-pull-0482])- Replaced most uses of
quanta::Instant
withstd::time::Instant
to increase the accuracy of time measurements (#481[gh-pull-0481]):
- When
quanta
feature is enabled,quanta::Instant
is used for some performance critical parts in the cache, andstd::time::Instant
is used for the rest of the parts.- However, as of this version, enabling the
quanta
feature will not make any noticeable difference in the performance.- When
quanta
feature is disabled (default),std::time::Instant
is used for all time measurements.- Switched to
AtomicU64
of theportable-atomic
crate, which provides fallback implementations for platforms wherestd
AtomicU64
is not available (#480[gh-pull-0480]):
moka
'satomic64
feature no longer has any effect on the build asAtomicU64
is now always available on all platforms. But we keep theatomic64
feature inCargo.toml
for backward compatibility.
de0b2d6
Merge pull request #483 from
moka-rs/prepare-v0-12-10c7aec09
Update the README; remove a broken link to the troubleshooting
section101e3a9
Merge pull request #482 from
moka-rs/disable-quanta-by-default9764df5
Merge pull request #481 from
moka-rs/increase-time-accuracy5d03e02
Minor tweaks in the clock module5dbd7ab
Merge pull request #480 from
moka-rs/portable-atomicf7d2d29
Update the change log0a6b6a4
Disable the quanta
feature by defaultd22f4f3
Update the change log668bdc0
Remove commented out codes