Skip to content

Latest commit

 

History

History
34 lines (22 loc) · 1.1 KB

RELEASE.md

File metadata and controls

34 lines (22 loc) · 1.1 KB

Releasing

Release process is automated in the pipeline with the following steps.

Test

We run the test workflow on:

  • Pull Request changing
    • any **.fish ;
    • and workflow (*.yml) files ;
  • on master branch changing
    • **.fish files with the exception conf.d/pure.fish, as we have dedicated mechanism to manage versions bump ;
    • and workflow (*.yml) files

Versioning

required: Commits must follow conventional commits convention.

Versioning is done automatically based on commit messages and triggered only on master branch.

Details:

  1. We compute the project's next version using a GitHub Action ;
  2. Then update $pure_version value in ./conf.d/pure.fish ;
  3. Finally commit and push the change to the repo.

Adding new tag

The add-version-tag.yml pipeline is triggered only for master when ./conf.d/pure.fish is changed and add a tagged based on $pure_version.