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

Full release process support #136

Open
marc0s opened this issue Jun 7, 2024 · 0 comments · May be fixed by #138
Open

Full release process support #136

marc0s opened this issue Jun 7, 2024 · 0 comments · May be fixed by #138

Comments

@marc0s
Copy link

marc0s commented Jun 7, 2024

In addition to #31 I'd like to have a tool for Cutting a Release in the sense of:

  1. processing commits since last git (annotated?) tag pointing to a release, so we can determine if such a subset of commits imply a patch, minor or major release number and calculate it (based on commitizen as pointed out in Generate changelog entry from pre-defined commit format #31)
  2. based on the same subset of commits, use their information to build a list of CHANGELOG entries to be inserted into the existing (or newly created if missing) CHANGELOG.md file
  3. update mix.exs (and optionally an adjacent VERSION file) accordingly to the new computed version number
  4. commit these changes with a meaningful git commit message
  5. tag that commit with the computed version number
  6. push the commit and tag to the remote origin

I'm aware this is such a broadening of the scope of the project in its actual form, so feel free to discard or amend at will 😄

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

Successfully merging a pull request may close this issue.

1 participant