search

riker-rs / riker

Easily build efficient, highly concurrent and resilient applications. An Actor Framework for Rust.
https://riker.rs
MIT License
1.02k stars 69 forks source link

create tags for releases #116

Open igalic opened 4 years ago

igalic commented 4 years ago

currently, riker has 21 releases on crates.io and zero corresponding tags:

◆ riker git:(master) ❯❯❯ git pull 
Already up to date.
◆ riker git:(master) ❯❯❯ git status
On branch master
Your branch is up to date with 'origin/master'.

nothing to commit, working tree clean
◆ riker git:(master) ❯❯❯ git tags
◆ riker git:(master) ❯❯❯

(or github releases)

it would be good to have an easy correlation between releases on crates.io in git when debugging a regression, and tags are exactly that.

nothingismagick commented 3 years ago

Now that there is a GH Action workflow integrated, there is a relatively trivial approaches to do automated releases:

  1. Make a dev branch that is the new default
  2. When ready to make a new release create and merge a PR to master
  3. If this merge passes all tests / example runs / etc. when merged create a new tagged release on GH releases
  4. Publish to crates.io
nothingismagick commented 3 years ago

That will require that a crates.io token is stored as a GH secret though... If there is interest I can see about making another PR that shows how it could work. Unfortunately it will require some marginal restructuring of the repo (new branch dev and dev as default and protecting the master branch from direct pushes...)

ForsakenHarmony commented 3 years ago

Is there even a changelog?