Skip to content

Latest commit

 

History

History
33 lines (24 loc) · 1.22 KB

RELEASING.md

File metadata and controls

33 lines (24 loc) · 1.22 KB

Release Process

Versioning is using MinVer. No changes in the code are needed to correctly version this package.

  1. Update the version in the following files:

  2. Update the CHANGELOG.md with the new release.

  3. Create a pull request on GitHub with the changes described in the changelog.

    • *scripts* and validate-documentation jobs will fail because the release is not published yet.
  4. Once the pull request has been merged, create a signed tag for the merged commit. You can do this using the following Bash snippet:

    TAG='v{new-version-here}'
    COMMIT='{commit-sha-here}'
    git tag -s -m $TAG $TAG $COMMIT
    git push upstream $TAG

    After you've pushed the git tag, a ci GitHub workflow starts.

  5. Publish a release in GitHub: