Skip to content

Commit 05d56ba

Browse files
committed
update changelog and ex
1 parent fb606a6 commit 05d56ba

2 files changed

Lines changed: 10 additions & 1 deletion

File tree

CHANGELOG.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,15 @@ All notable changes to this project will be documented in this file.
44
The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
55
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
66

7+
## [0.3.4] - UNRELEASED
8+
9+
### Added
10+
- `unsupported` opt-in backend [#667]
11+
12+
[#667]: https://github.com/rust-random/getrandom/pull/667
13+
14+
[0.3.4]: https://github.com/rust-random/getrandom/compare/v0.3.3...HEAD
15+
716
## [0.3.3] - 2025-05-09
817

918
### Changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -207,7 +207,7 @@ unsafe extern "Rust" fn __getrandom_v03_custom(
207207
### Unsupported backend
208208

209209
In some rare scenarios you might be compiling this crate in a constrained
210-
environment (ex. `wasm32-unknown-unknown`), but this crate's functionality
210+
environment (e.g. `wasm32-unknown-unknown`), but this crate's functionality
211211
is not actually used by your code. If you are confident that `getrandom` is
212212
not used in your project, but it gets pulled nevertheless by one of your
213213
dependencies, then you can enable the `unsupported` backend, which always

0 commit comments

Comments
 (0)