Skip to content

Conversation

@sirhcel
Copy link
Member

@sirhcel sirhcel commented Oct 23, 2025

The linux-embedded-hal exposes spidev and in order to fix rust-embedded/linux-embedded-hal#120, we need a patch release for 0.6. I already created the branch maintenance-0.6 and this PR backports #49 onto 0.6 and prepares release 0.6.1.

@sirhcel sirhcel requested a review from jannic October 23, 2025 10:18
@sirhcel sirhcel requested a review from a team as a code owner October 23, 2025 10:18

name = "spidev"
version = "0.6.0"
version = "0.6.2-alpha.0"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks wrong for the 0.6.1 release. Or am I somehow misunderstanding the release process?

Suggested change
version = "0.6.2-alpha.0"
version = "0.6.1"

Copy link
Member Author

@sirhcel sirhcel Oct 23, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Version 0.6.1 is set with 3e9b3b2. This is the revision I planned for tagging release 0.6.1 and releasing to crates.io from.

For the time after 0.6.1 ee8a1e5 attempts to cleanly state that the code in question is no longer 0.6.1 and there is less room for confusion.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah ok, that wasn't obvious when viewing the changes.

So this MR should be merged in "rebase and merge" mode, because "squash and merge" would destroy the intermediate commit, and the default mode "merge pull request" would create a slightly confusing commit history, right?

@sirhcel
Copy link
Member Author

sirhcel commented Oct 23, 2025

Rebased this PR onto #52.

@sirhcel sirhcel requested a review from jannic October 23, 2025 13:41
@sirhcel sirhcel merged commit b7903b6 into rust-embedded:maintenance-0.6 Oct 23, 2025
9 checks passed
@sirhcel sirhcel deleted the release-0.6.1 branch October 23, 2025 13:55
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