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.3.0 #22

Merged
merged 1 commit into from
Feb 26, 2025
Merged

Release v0.3.0 #22

merged 1 commit into from
Feb 26, 2025

Conversation

robin-nitrokey
Copy link
Member

No description provided.

@sosthene-nitrokey
Copy link
Contributor

Thinking about it, maybe add a compat-v1 feature that is enabled by default and required to be enabled to compile. That way we can have support for #15 in the future without a breaking release.

@robin-nitrokey
Copy link
Member Author

I’m not too worried about breaking littlefs2-sys releases as only very few crates depend on it. So I would prefer to keep things simple, release this as-is and just do another breaking release if we need to.

@sosthene-nitrokey
Copy link
Contributor

Yes that's right. And maybe we can switch littlefs2 releases to depend on one exact littlefs2-sys version like most proc-macro crates do.

@robin-nitrokey robin-nitrokey merged commit ed32886 into main Feb 26, 2025
6 checks passed
@robin-nitrokey robin-nitrokey deleted the release-v0.3.0 branch February 26, 2025 11:21
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