https://github.com/netchris/semver-pre-release

Facilitate pre-releases with SemVer enforcement
https://github.com/netchris/semver-pre-release

Last synced: about 1 month ago
JSON representation

Facilitate pre-releases with SemVer enforcement

• Host: GitHub
• URL: https://github.com/netchris/semver-pre-release
• Owner: NetChris
• Created: 2024-01-21T21:15:48.000Z (11 months ago)
• Default Branch: main
• Last Pushed: 2024-01-22T07:02:31.000Z (11 months ago)
• Last Synced: 2024-01-23T00:24:09.177Z (11 months ago)
• Size: 4.88 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 1
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# semver-pre-release

 

Enforce the ref for a pre-release.  The git ref:

- MUST be a SemVer version

- MUST have a pre-release version

## Using

``` yaml

name: Pre-Release

on:

  release:

    types: [prereleased]

jobs:

  publish_pre_release:

    runs-on: ubuntu-latest

    name: NAME

    steps:

      - name: Enforce SemVer for pre-release

        id: enforce_semver

        uses: NetChris/semver-pre-release@SHA

      - name: Use the SemVer version

        run: echo Do something with semver_version: ${{ steps.enforce_semver.outputs.semver_version }}

```

Use the latest (or most-appropriate) SHA to ensure consistent results.

## Notes

Although not a concern of this action, it's important to point out an issue with the `prereleased` release type.  From [the GitHub documentation](https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#release), there is an issue releasing a _draft_ pre-release:

> Note: The prereleased type will not trigger for pre-releases published from draft releases, but the published type will trigger. If you want a workflow to run when stable and pre-releases publish, subscribe to published instead of released and prereleased.