update version to 0.5.0

[philolo1]

No description provided.

[sylvestre]

I think cargo.lock needs to be updated too, no?

[philolo1]

@sylvestre updated.

[sylvestre]

i wish your update of cargo.lock didn't update many dependencies in this PR

[philolo1]

@sylvestre i just ran "cargo update", is there another way? My guess is that chrono has quite some dependency changes. I don't remember adding any library.

[tertsdiepraam]

@philolo1 Just cargo test or something like that should fix Cargo.lock right? Idk, maybe I'm confused. cargo update is specifically for updating all dependencies to the highest versions in Cargo.toml

[philolo1]

@tertsdiepraam @sylvestre if i run cargo test there is no change to cargo lock file. I don't think the cargo lock file has any reference to the cargo version. I can set it back to not changing the lock file. Unfortunatly i don't have to much experience with rust release system.

[tertsdiepraam]

Well, this should be in there at least. Is that not changed either?

[tertsdiepraam]

Oh and the fuzz/Cargo.lock should be updated too I guess.

[philolo1]

thanks @tertsdiepraam

[cakebaker]

Maybe it's cargo update -p <package-name> you are looking for?

[philolo1]

@cakebaker thanks.
@tertsdiepraam @sylvestre thanks for the comments, i think i now updated only parse_datetime and fuzz.

[philolo1]

@tertsdiepraam @sylvestre any updates, i would like to close the pr's i have here.

[sylvestre]

oups, sorry :(

[sylvestre]

ok to publish on crates.io ?

[philolo1]

Yes

…

On Fri, Sep 15, 2023 at 0:51 Sylvestre Ledru ***@***.***> wrote: ok to publish on crates.io ? — Reply to this email directly, view it on GitHub <#46 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABP4LZV3V2K2K6YOX4HKDJDX2MRX7ANCNFSM6AAAAAA4JU6G3A> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[sylvestre]

live: https://crates.io/crates/parse_datetime