fortinet/Resolve a version branch

Resolve a version branch by semver strategies. Create one if not exists. Return the head branch and the details of the new version.

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
Runtime
Deprecated runtime
namedescriptionrequireddefault
github-tokenThe GitHub token to authorize actions on behalf of users.yes
base-branchThe base branch that a versioning branch will be based.yes
name-prefixThe name prefix to include in the new branch name. The new branch name format is: <prefix><version>. Example: Rel_branchv1.0.0-rc.1 The version will be retrieved from the base-branch, bumped according to the version-level.norel_
version-levelThe level of the semver version. Accepted inputs: major, minor, patch, and prerelease.no
pre-idA valid semver pre-release identifier. Used in command: npm version --preid=<pre-id> If specified, the versioning behavior will become 'premajor', 'preminor', 'prepatch', and 'prerelease'.no
custom-versionThe custom version to bump to. If specified, it will be used as the version. It needs to be a valid semver format.no
pr-numberThe pull request number for info retrieval uses. If present, the information will be returned in the action output, and no new branch will be created as opposed to creating a new branch by default without the pr-number.no
namedescription
base-branchThe branch that a versioning branch is based.
base-versionThe version found in the base branch.
head-branchThe versioning branch.
head-versionThe version tag used for the versioning branch.
is-new-branchA boolean indicator for whether the head branch is a new branch or not.
is-prereleaseA boolean indicator for whether the version is resolved as a prerelease or not.
majorThe major version of the new version.
minorThe minor version of the new version.
patchThe patch version of the new version.
pre-idThe non-incremental part of the new version, if it is a prerelase.
pre-incThe incremental part of the new version, if it is a prerelase.