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

Update embassy-time 0.3 -> 0.4 #219

Merged
merged 3 commits into from
Jan 16, 2025
Merged

Update embassy-time 0.3 -> 0.4 #219

merged 3 commits into from
Jan 16, 2025

Conversation

ivmarkov
Copy link
Contributor

@kedars

Minimal change that does only what the subject says.

However, very important because the change in embassy-time was of such a nature, that in your whole cargo tree you do need to have either embassy-time <= 0.3 or embassy-time >= 0.4 (but cannot have both).
(Basically, they changed their "time driver" API, which should not happen again any time soon.)

Since embassy-time is popular, and all crates depending on it are mass-updating to 0.4, we need to do it too, or else rs-matter cannot be used in one and the same project with these updated crates.

Copy link

semanticdiff-com bot commented Jan 15, 2025

Review changes with  SemanticDiff

Changed Files
File Status
  README.md Unsupported file format
  rs-matter/Cargo.toml Unsupported file format
  rs-matter/tests/common/e2e/im/echo_cluster.rs  0% smaller

@ivmarkov ivmarkov requested a review from kedars January 15, 2025 20:44
@ivmarkov
Copy link
Contributor Author

Ready for review.

@kedars kedars merged commit 3230519 into project-chip:main Jan 16, 2025
12 checks passed
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