Resolve "Rename duniter-wotb crate to durs-wot"

Closes #71 (closed)

added 1 commit

• d8d1fee4 - Rename duniter-wotb to duniter-wot

Compare with previous version

Please rename it rather durs_wot.

In addition, renaming a crate also asks to publish the old crate as deprecated on crates.io and then to publish the new one.

I had started a general renaming of the project as a "runiter", then I changed my mind, but in the meantime I had published the crate runiter_wot and declared the crate duniter_wotb depreciated.

So it's a mess so I'll take care of the crates.io part, I'll just let you know so you know that you'll have to do it if you can rename crates again;)

Could we use the CI to publish crates on crates.io on updates ?

added 1 commit

• e63713e1 - Rename duniter-wotb to durs-wot

Compare with previous version

changed title from Resolve "Rename duniter-wotb crate to duniter-wot" to Resolve "Rename duniter-wotb crate to durs-wot"

@Insoleet yes you can use the CI :

• push a new tag named wot/v0.8.0-a0.8 in this branch
• The publish_crate job appears in pipeline
• You must launch manually this job after making sure that all tests pass and that the code formatting is correct.

added 2 commits

• 79bf8071 - 1 commit from branch dev
• c7c2b260 - Rename duniter-wotb to durs-wot

Compare with previous version

added 1 commit

• 4b988cb5 - Rename duniter-wotb to durs-wot

Compare with previous version

I push comply of new fmt version in dev and rebase this branch.

Thank you very much for this contribution, it's ok for me :)

You can push tag wot/v0.8.0-a0.8 and publish new crate ;)

Oooops I did a really bad mistake - I pushed the tag on the wrong branch (the issue 70 instead of 71...)

Can you delete it ?

https://git.duniter.org/nodes/rust/duniter-rs/tags/wot%2Fv0.8.0-a0.8

Unfortunately it's not possible to delete a tag, so I cancelled the pipelines launched by wrong branch that's all we can do.

Also, you will have to increment the version of the wot crate because you can't push the same tag twice ;)

Fortunately the publish_crate job is manual, it helps to avoid this type of human error !

added 1 commit

• daa822d3 - Version 0.8.0-a0.9

Compare with previous version

Ok I pushed the new version, I'll let you check and publish to crates.io.

mentioned in commit 8d216a60

merged