Skip to content

Latest commit

 

History

History
47 lines (34 loc) · 1.36 KB

RELEASE.md

File metadata and controls

47 lines (34 loc) · 1.36 KB

Release

  • Update dependencies and fix any outdated dependencies. (can be skipped as Dependabot keeps everything updated)
npm install -g npm-check-updates
npm-check-updates
  • Ensure the CHANGELOG is up-to-date.

  • If this release is a major version, update all the example YAML in the README, e.g. 4.0.0 would need @v3 -> @v4.

  • Ensure that all workflow runs for the latest commit on main are green.

  • Create a new release via "Draft a new release" button at the Release page:

    • Choose a new tag like vX.Y.Z that targets the current main branch and that is created on publish of the release
    • Choose the title Version X.Y.Z
    • Paste the relevant CHANGELOG section into the description field
    • Publish the release

Replace X.Y.Z by the appropriate version number.

  • Point the old vX tag to latest vX.Y.Z tag:
git remote update
git tag -d vX
git push origin :refs/tags/vX
git checkout vX.Y.Z
git tag -a vX -m 'Release version vX.Y.Z'
git push origin --tags

Replace X.Y.Z by the appropriate version number.

  • Update the old repository just in case with the main/master branch

https://github.com/goanpeca/setup-miniconda