kevin/asdf
1
Fork 0
mirror of https://github.com/asdf-vm/asdf.git synced 2024-11-15 09:38:16 -07:00
Code Issues Packages Projects Releases Wiki Activity
34593c1766
asdf/release
History
James Hegedus 2bf076f3d3
fix: docs file rename (#809) 
We renamed the documentation to refer to `asdf` the tool itself instead of `asdf-vm`. We forgot to update the release script.
2020-09-29 08:46:40 +10:00
..
README.md Update release.sh script so it checks for RC tags before tagging new major and minor versions 2019-03-24 17:17:51 -04:00
tag.sh fix: docs file rename (#809) 2020-09-29 08:46:40 +10:00

README.md

Release README

If you are a user you can ignore everything in this directory. This directory contains documentation and scripts for preparing and tagging new versions of asdf and is only used by asdf maintainers.

Tagging Release Candidates

To tag release candidates

  1. Update the CHANGELOG. Make sure it contains an entry for the version you are tagging as well as a dev version things that come after the tag (e.g. a heading with the format <next-version>-dev).
  2. Run the tests and the linter - bats test and lint.sh.
  3. Run the release script. The new version must be in the format 0.0.0-rc0. For example: release/tag.sh 0.0.0-rc0.
  4. If the release script succeeds, push to Github. Make sure to use the correct remote to push to the official repository

Tagging Releases

  1. Update the CHANGELOG. Make sure it contains an entry for the version you are tagging as well as a dev version things that come after the tag (e.g. a heading with the format <next-version>-dev).
  2. Run the tests and the linter - bats test and lint.sh.
  3. Run the release script. The new version must be in the format 0.0.0. For example: release/tag.sh 0.0.0.
  4. If the release script succeeds, push to Github. Make sure to use the correct remote to push to the official repository