0.13.2 bindgen introduces arbitrary feature gate

[Indeximal]

Combined with our --Deny Warnings lead our CI to spontaneous break. Adding feature gates to generated code doesn't seem particularly smart to me, since you can in/exclude it with options in the build script. Additionally, it now means the cargo toml of the crate using mavlink-bindgen has to be updated to make use of the new feature anyway, as the dependencies are not automatically used (e.g. by reexporting them in mavlink-bindgen).

Please be more careful with minor changes, a lot of things can be breaking.

[joaoantoniocardoso]

I'm not sure if I understood the message. The 'arbitrary' feature should be on 0.14.0, not 0.13.2. But mainly, since there's no stable version (as in.. we are using 0.x.x), a minor version will most certainly have breaking changes, otherwise it's set as a patch.

[Indeximal]

But mainly, since there's no stable version (as in.. we are using 0.x.x)

This is not how semver works. 0.x.y means that 0.x.z is comatible and 0.x+1.y is breaking.

The 'arbitrary' feature should be on 0.14.0, not 0.13.2

The crates.io for mavlink-bindgen shows 0.13.2 go published, not 0.14.0.

Edit: sorry if the tone sounded harsh, I appreciate your work :)

[pv42]

There was a issue with the release and what should have been published as 0.14 didn't get properly version bumped.

[patrickelectric]

0.13.2 and 0.14.0 will be removed, the new version 0.14.1 should be used

[joaoantoniocardoso]

This is not how semver works. 0.x.y means that 0.x.z is comatible and 0.x+1.y is breaking.

Good, this was precisely what I meant by "minor" vs "patch".

[joaoantoniocardoso]

0.13.2 and 0.14.0 will be removed, the new version 0.14.1 should be used

Just to note, the version 0.13.2 from crates.io is wrong, having the arbitrary feature. The git tag 0.13.2 is correct.