Skip to content
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.

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

chore(deps): update rust crate bytemuck to v1.17.0 #235

Merged

Conversation

renovate-bot
Copy link
Contributor

@renovate-bot renovate-bot commented Aug 16, 2024

Mend Renovate

This PR contains the following updates:

Package Type Update Change
bytemuck workspace.dependencies minor 1.16.3 -> 1.17.0

Release Notes

Lokathor/bytemuck (bytemuck)

v1.17.0

Compare Source

  • Makes the must_cast versions of the by-value and by-ref casts be const.
    The mut ref cast is unaffected for now (mut references aren't yet stable in const fn).
    This increases the MSRV of using that particular feature from 1.57 to 1.64.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate-bot renovate-bot force-pushed the renovate/bytemuck-1.x-lockfile branch from bf64fb3 to 3bf8996 Compare August 22, 2024 22:49
@nicholasbishop nicholasbishop enabled auto-merge (rebase) August 22, 2024 22:50
@nicholasbishop nicholasbishop merged commit 0b81625 into google:main Aug 22, 2024
12 checks passed
@renovate-bot renovate-bot deleted the renovate/bytemuck-1.x-lockfile branch August 22, 2024 22:54
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.

2 participants