janked dependencies: bump critical-section, atomic-polyfill, heapless#567
Merged
Conversation
Freax13
approved these changes
Jun 25, 2026
Freax13
left a comment
Freax13
left a comment
Member
There was a problem hiding this comment.
Thank you for your contribution!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We currently rely on dependencies that are janked on crates.io. This causes warning when the bootlader is installed using the locked flag as is done in build.rs.
This PR bumps critical-section and atomic-polyfill. Also heapless gets bumped as it requires an exact version of atomic-polyfill so it needs to be bumped for cargo to accept a newer version of atomic-polyfill.
Not sure what the best practices are here. It looks like updates to Cargo.lock in this repo seem to only change versions of specific crates when needed. Maybe a clean
cargo updateshould be done at some point, considering the bootloader is installed using--locked.