alazhar/gitea-autorelease

Automatically detect new tags for new versions and create release

Trust Signals

workflow.ymlSHA-pinned

uses: alazhar/gitea-autorelease-action@5bf9340924b34d6312e643d36dddc5e5a6c07817 # no releases — HEAD as of 2026-07-13

tags can be moved; commit SHAs can't. why a SHA?

name	description	required	default
filepath	Autotag will look for the appropriate file in in this location (relative to project root).	yes	—
regex_pattern	An optional attribute containing the regular expression used to extract the version number.	yes	—
tag_prefix	By default, package.json uses semantic versioning, such as "1.0.0". A prefix can be used to add text before the tag name. For example, if tag_prefx is set to "v", then the tag would be labeled as "v1.0.0".	no	—
log_template	The commit message template (per commit). Default is `{{number}}) {{message}} ({{author}}) SHA: {{sha}} `	no	—
release_name	Gives the release a custom name. Defaults to tag name	no	${{ github.ref_name }}
draft	Creates a draft release. Defaults to false	no	true
release_attachment	Newline-delimited list of path globs for asset files to upload	no	—
md5sum	Publish `.md5` along with artifacts.	no	—
sha256sum	Publish `.sha256` along with artifacts.	no	—

name	description
tagname	Returns the new tag value. Empty if a tag is not created.
version	The version, as defined in package.json or explicitly set in the input.
prerelease	Is the new version prerelease.
release_url	Release location.