Release request

[h7x4]

Hello!

I've created a PR further downstream that depends on some features that have yet to be released. It seems like last release was March 26th, and a few commits has been made in between.

Would you mind creating a small version bump?

[a1ien]

I will but not early than next week.

…

On Mon, Jul 17, 2023, 15:00 Øystein Tveit ***@***.***> wrote: Hello! I've created a PR further downstream that depends on some features that have yet to be released. It seems like last release was March 26th, and a few commits has been made in between. Would you mind creating a small version bump? — Reply to this email directly, view it on GitHub <#173>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACERWR6CW3H3D5RNQSSK53XQUSONANCNFSM6AAAAAA2M2U4EM> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[h7x4]

Great! Thank you

[h7x4]

Friendly ping 😁

[a1ien]

Sorry. Yes make release on this week. The only thing stop me to doing it need to prepare changelog. If you really want to make release faster you can create PR with changelog :)

…

On Wed, Aug 23, 2023, 13:28 Øystein Tveit ***@***.***> wrote: Friendly ping 😁 — Reply to this email directly, view it on GitHub <#173 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACERWSIMN3S2T7JTBY2RS3XWXLNVANCNFSM6AAAAAA2M2U4EM> . You are receiving this because you commented.Message ID: ***@***.***>

[h7x4]

I've added a new PR #178 with changelog and stuff.

I noticed that Cargo.toml still specifies libusb1-sys.version = "0.6.0" despite last release of this crate being 0.6.3. Is there a reason behind this?

[a1ien]

I think we should update libusb1-sys.version to 0.6.3

[h7x4]

Turns out I was just confusing myself. It's ignoring the patch number already (i.e. Cargo.lock says libusb1-sys 0.6.4), but I've made a PR #179 to make it more obvious.