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

Preparations for release 0.10.1 #796

Closed
wants to merge 6 commits into from
Closed

Preparations for release 0.10.1 #796

wants to merge 6 commits into from

Conversation

9names
Copy link
Member

@9names 9names commented Apr 28, 2024

Update CHANGELOG.md
Set version to 0.10.1 in preparation for the release

This is a rebase of changes from main on top of 0.10.0, excluding PIO DMA changes:

Here is the selection of commits used via rebase -i

pick 4a677a6 Simplify ceiling division in delay calculation
pick caa0ea0 Fix float_to_fix64 return value & docs for f32 trig functions
drop 9947302 Enable transfer size of PIO DMA to be specified
drop 6ce5672 Add some more type params
drop caaef72 Remove type params on `build` to avoid inference failures
drop 36a05f2 Fix Tx::transfer_size
drop efe574a Move TransferSize to `dma` module
pick 48dbfcc Slightly improve deprecation note on from_program
pick effcc46 Fix debugging after halt()
pick 0d819d3 Implement embedded_io traits for Reader/Writer
pick 8e15127 Implement `send_break` support

Leaving this as a draft PR so it doesn't get merged. Will tag the final commit hash as v0.10.1 and close this PR when reviewed.

Text-Input and others added 6 commits April 28, 2024 11:19
The current return argument for float_to_fix64 doesn't
make sense and is at odds with the definition in the SDK.
Replace it with the correct type.

Similarly, the function descriptions for fcos, fsin, and ftan
give a valid range inconsistent with the values given
on page 140 of thedatasheet. This corrects them.
@9names
Copy link
Member Author

9names commented Apr 28, 2024

Did a cargo publish --dry-run, yielded this warning:

warning: package `atomic-polyfill v0.1.11` in Cargo.lock is yanked in registry `crates-io`, consider updating to a version that is not yanked

Ah, we don't publish a lock file for rp-hal, so this is all local issues.

@jannic
Copy link
Member

jannic commented Apr 28, 2024

LGTM. Compared it with the main branch which didn't show up unexpected differences, so all actual code on this branch has already been reviewed before being merged to main.

CARGO_BUILD_TARGET=x86_64-unknown-linux-gnu cargo semver-checks doesn't complain. That doesn't prove the absence of breaking changes (especially it doesn't detect the change to float_to_fix64 which is formally a breaking change, but it's fine because it's fixing a bug and the code with the old signature was just broken.)

Changelog looks complete and accurate.

@9names
Copy link
Member Author

9names commented Apr 28, 2024

Tagged and released this version as v0.10.1

@9names 9names closed this Apr 28, 2024
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.

4 participants