Skip to content

Why does git have cortex-m version stated as 0.7.4 while crate is at 0.7.7? #579

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

Closed
k-bx opened this issue Feb 9, 2025 · 2 comments
Closed

Comments

@k-bx
Copy link

k-bx commented Feb 9, 2025

Quite confusing. Is this intended?

@jannic
Copy link
Member

jannic commented Feb 9, 2025

The master branch of this repo contains what will become cortex-m 0.8.0. After the first breaking change was merged, there were several minor updates released from branch v0.7.x, so that's where you find the sources of version 0.7.7.
https://github.com/rust-embedded/cortex-m/tree/v0.7.x

Yes, it can be a bit confusing. It's not an unusual approach, but it's a bit unfortunate that version 0.8.0 takes so long.

@k-bx
Copy link
Author

k-bx commented Feb 10, 2025

Roger. It's just more usual to have master contain either the most recent commits from other repos (so to have 0.7.7 version), or to have a version 0.8.0, or to have 0.8.0-alpha etc, so it's easy to just put master branch commit in your Cargo.toml and it would just work, for me it errored because of that.

Anyways, doing a fork and editing version was easy enough. Closing this one.

@k-bx k-bx closed this as completed Feb 10, 2025
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

No branches or pull requests

2 participants