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

Release v0.5.0 #85

Merged
merged 1 commit into from
Oct 25, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion .github/workflows/ci.yml
Original file line number Diff line number Diff line change
Expand Up @@ -108,7 +108,9 @@ jobs:
EOT

- name: Patch delog
run: echo 'delog = { version = "0.1.6", git = "https://github.com/LechevSpace/delog.git", rev = "e83f3fd" }' >> Cargo.toml
run: |
echo '[patch.crates-io]' >> Cargo.toml
echo 'delog = { version = "0.1.6", git = "https://github.com/LechevSpace/delog.git", rev = "e83f3fd" }' >> Cargo.toml
Comment on lines +111 to +113
Copy link
Contributor

Choose a reason for hiding this comment

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

Not really the fault of this PR but Why does this point to a custom branch?  We should merge the related PR no?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes. But I wanted to do some more tests for the delog PR and did not want to delay the littlefs2 PR (with breaking changes to be included in the releases) until delog is ready.


- name: Build avr
run: cargo +nightly build -Z build-std=core --target=./avr-atmega328p.json --workspace --release
8 changes: 8 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,14 @@ and this project adheres to [Semantic Versioning](http://semver.org/).

## Unreleased

-

## [v0.5.0](https://github.com/trussed-dev/littlefs2/releases/tag/0.5.0) - 2024-10-25

This release contains many small changes to the public API. It also introduces the
`littlefs2-core` crate that can be used for crates that want to access `littlefs2`
filesystems without depending on a specific implementation version.

### Added
- Added object-safe traits `DynFile`, `DynFilesystem` and `DynStorage` for
accessing `Storage`, `Filesystem` and `File` implementations for any storage.
Expand Down
5 changes: 1 addition & 4 deletions Cargo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ repository = "https://github.com/trussed-dev/littlefs2"
[package]
name = "littlefs2"
description = "Idiomatic Rust API for littlefs"
version = "0.4.0"
version = "0.5.0"
authors = ["Nicolas Stalder <[email protected]>", "Brandon Edens <[email protected]>", "The Trussed developers"]
readme = "README.md"
categories = ["embedded", "filesystem", "no-std"]
Expand Down Expand Up @@ -52,6 +52,3 @@ log-error = []
# member `char name[LFS_NAME_MAX+1]`.
# This means that if we change `traits::Storage::FILENAME_MAX_PLUS_ONE`,
# we need to pass this on!

[patch.crates-io]
littlefs2-sys = { git = "https://github.com/trussed-dev/littlefs2-sys.git", tag = "0.2.0" }
Loading