This action lets you control releases and tags through the version number in your project files
(Cargo.toml, package.json, or version.txt).
It does this by comparing the version on file with the release tag supplied as input, which is meant to be
supplied by another action that reads the latest release tag from the repository.
If the version on file is higher than the release tag supplied, `should-release` output will be set to `true`
and `current_version` output will be set to the version on file. The next step in the workflow can then use those
outputs to trigger a Github release and build artifacts as needed.
If the version on file is lower or equal to the `release_tag` input, `should-release` output will be set to `false`.
the release tag to compare with, defaults to v0.0.0 if not supplied or empty. That default essentially means
always release, which is useful for the first release of a project
—
—
Outputs
name
description
should_release
true if the version on file is higher and release should be made, false otherwise
current_version
the version on file, should be used to create a release tag by the next step in the workflow