Release deployment

[brainstorm]

Inspired by the commits I've seen over https://github.com/rust-bio/rust-htslib/blob/master/.github/workflows/release-please.yml.

Ideally we should be using googleapis/release-please#954 as a way to easily publish all sub-crates within this repo, instead of enumerating each one.

Fixes issue #29

/cc @sstadick

[brainstorm]

Actually, that release-please PR is just a wrapper around https://github.com/fasterthanlime/cargo-workspaces#publish... so I guess we could just use that in the meantime to publish all crates within the noodles workspace.... OTOH the PR above seems to be very close to being merged.

[sstadick]

An alternative method: https://github.com/BurntSushi/ripgrep/blob/master/RELEASE-CHECKLIST.md where something like cargo workspace publish is just run locally.

In the yaml I am personally a fan of only triggering on tags of some sort https://github.com/sstadick/perbase/blob/030904f6178f3fd4c10fcc97379d072abb0b39e4/.github/workflows/main.yml#L5, or v.* as the pattern.

edit to add why I like to trigger on tags it allows for updating the readme on master without needing to do a release.

[brainstorm]

Thanks @sstadick! By the comment on #29 I'd guess that @zaeleus might publish the first version manually this week before automating it? In any case, let's see which option he prefers from the ones described here.

[sstadick]

I'm happy regardless of the method a release happens, and super excited to see a version of this on crates.io!

[zaeleus]

Thanks, but I'd like to publish manually for now, particularly to better understand the process when managing many interdependent crates. For example, there's a small delay between a successful publication and when you can actually use the crate, which can make an automated publication of a crate that depends on it fail. I also learned that crates.io enforces a rate limit after 5 pushes. :P

error: failed to publish to registry at https://crates.io

Caused by:
  the remote server responded with an error (status 429 Too Many Requests): You
  have published too many crates in a short period of time. Please try again
  after Wed, 14 Jul 2021 22:34:44 GMT or email help@crates.io to have your limit
  increased.

[brainstorm]

Yeah, I understand, those gotchas from crates.io are indeed unexpected.

I wonder how @fasterthanlime deals with that kind of rate limiting and dependency (timing) failures when using the recently merged googleapis/release-please#954.

[fasterthanlime]

We use "cargo workspaces publish", which polls the registry after publishing to wait for it to really show up.

We publish to a private Cloudsmith registry so we haven't run into the crates.io rate limiting!

[zaeleus]

Just for future reference, I talked to a crates.io team member. He clarified that there is a 5 new crate burst publication rate limit and a 30 existing crate burst publication rate limit (1 publication/minute).