Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

create tags for releases #116

Open
igalic opened this issue Jun 20, 2020 · 3 comments
Open

create tags for releases #116

igalic opened this issue Jun 20, 2020 · 3 comments

Comments

@igalic
Copy link
Contributor

igalic commented Jun 20, 2020

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
Copy link
Contributor

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
Copy link
Contributor

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
Copy link

Is there even a changelog?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants