Navigation

• Parsing
• Using a result
• Options
• Outputs
• Contrubuting
• Maintenance
  • Regular flow
  • Prerelease from
  • Conventions

Parsing

steps:
  # 1. from workflow tag (can be v-prefixed)
  # good for release workflows and pushing tags
  - name: Parse version from tag
    id: version
    uses: release-kit/semver@v2
  
  # 2. from manually defined v-prefixed string
  - name: Parse version from string
    id: version
    uses: release-kit/semver@v2
    with:
      string: 'v4.5.0'

  # 3. from a string with the custom pattern
  - name: Parse version from a string with a custom pattern
    id: version
    uses: release-kit/semver@v2
    with:
      string: 'my-version:4.5.0'
      pattern: '^my-version:(.*)$' # ^v?(.*)$ by default

  # 4. from a tag with the custom fallback
  # the fallback is used when there is no tag found
  # works only for "latest-tag" source
  - name: Parse version from tag with custom fallback
    id: version
    uses: release-kit/semver@v2
    with:
      source: latest-tag
      fallback: 'v1.0.0' # v0.1.0 by default

Using a result

- name: Use parsed version
  run: |
    echo "${{ steps.version.outputs.major }}"
    echo "${{ steps.version.outputs.minor }}"
    echo "${{ steps.version.outputs.patch }}"
    echo "${{ steps.version.outputs.prerelease }}"
    echo "${{ steps.version.outputs.build }}"
    echo "${{ steps.version.outputs.full }}"

Check out the Outputs section for the full description.

Options

• source (optional, defaults to workflow-tag)
  • workflow-tag - use tag from the workflow event (good from releases and tag pushes)
  • latest-tag - use the latest tag from current repository (requires executing checkout action first)
  • string - use the value from string input (can be omitted, automatically selected when string is defined)
• string (optional, defaults to empty) - a string to be parsed, required only when source is string
• fallback (optional, defaults to v0.1.0) - fallback string when a tag is not found
• pattern (optional, defaults to ^v?(.*)$) - regex to extract a version from a string

Outputs

• full - 3.4.5-alpha+1.2 in v3.4.5-alpha+1.2
• major - 3 in v3.4.5-alpha+1.2
• minor - 4 in v3.4.5-alpha+1.2
• patch - 5 in v3.4.5-alpha+1.2
• prerelease - alpha in v3.4.5-alpha+1.2 (empty string if no present)
• build - 1.2 in v3.4.5-alpha+1.2 (empty string if no present)

Contributing

1. Fork this repo
2. Use the Regular flow

Please follow Conventions

Maintenance

The dev branch is main - any developer changes is merged in there.

Also, there is a release/latest branch. It always contains the actual source code for release published with latest tag.

All changes is made using Pull Requests - push is forbidden. PR can be merged only after successfull test-and-build workflow checks.

When PR is merged, release-drafter workflow creates/updates a draft release. The changelog is built from the merged branch scope (feat, fix, etc) and PR title. When release is ready - we publish the draft.

Then, the release workflow handles everything:

• It runs tests, builds a package, and publishes it
• It synchronizes released tag with release/latest branch

Regular flow

1. Create feature branch
2. Make changes in your feature branch and commit
3. Create a Pull Request from your feature branch to main
   The PR is needed to test the code before pushing to release branch
4. If your PR contains breaking changes, don't forget to put a BREAKING CHANGES label
5. Merge the PR in main
6. All done! Now you have a drafted release - just publish it when ready

Prerelease flow

1. Assume your prerelease tag is beta
2. Create release/beta branch
3. Create feature branch
4. Make changes in your feature branch and commit
5. Create a Pull Request from your feature branch to release/beta
   The PR is needed to test the code before pushing to release branch
6. Create Github release with tag like v1.0.0-beta, pointing to release/beta branch
   For next beta versions use semver build syntax: v1.0.0-beta+1
7. After that, the release workflow will publish your package with the beta tag
8. When the beta version is ready to become latest - create a Pull Request from release/beta to main branch
9. Continue from the Regular flow's #5 step

Conventions

Feature branches:

• Should start with feat/, fix/, docs/, refactor/, and etc., depending on the changes you want to propose (see pr-labeler.yml for a full list of scopes)

Commits:

• Should follow the Conventional Commits specification

Pull requests:

• Should have human-readable name, for example: "Add a TODO list feature"
• Should describe changes
• Should have correct labels