8000 Don't use proptest deprecated methods by UMR1352 · Pull Request #1676 · iotaledger/identity · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Don't use proptest deprecated methods #1676

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Jun 10, 2025
Merged

Don't use proptest deprecated methods #1676

merged 1 commit into from
Jun 10, 2025

Conversation

UMR1352
Copy link
Contributor
@UMR1352 UMR1352 commented Jun 10, 2025

Description of change

Latest version of proptest deprecated some methods, switch to the new ones.

@UMR1352 UMR1352 self-assigned this Jun 10, 2025
@UMR1352 UMR1352 requested a review from a team as a code owner June 10, 2025 08:45
@UMR1352 UMR1352 added the Chore Tedious, typically non-functional change label Jun 10, 2025
@eike-hass eike-hass added Rust Related to the core Rust code. Becomes part of the Rust changelog. Patch Change without affecting the API that requires a patch release. Part of "Patch" section in changelog labels Jun 10, 2025
@UMR1352 UMR1352 merged commit 70d3fd1 into main Jun 10, 2025
12 of 15 checks passed
@UMR1352 UMR1352 deleted the fix/proptest-deprecated-methods branch June 10, 2025 10:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@eike-hass eike-hass eike-hass approved these changes

Assignees

@UMR1352 UMR1352

Labels
Chore Tedious, typically non-functional change Patch Change without affecting the API that requires a patch release. Part of "Patch" section in changelog Rust Related to the core Rust code. Becomes part of the Rust changelog.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@UMR1352 @eike-hass
0