kuddy-on/Gitea Release Please

A single-package Google Release Please compatible action for Gitea.

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
tokenGitea Actions GITEA_TOKEN or a token with repository write access.yes
gitea-urlGitea server root or API v1 URL. Defaults to GITEA_SERVER_URL.no
repositoryRepository in owner/name form. Defaults to GITEA_REPOSITORY.no
repo-urlGoogle-compatible alias for repository.no
proxy-serverHTTP or HTTPS proxy used for Gitea API requests, as host:port or a full URL.no
forkCreate and manage the Release PR branch in the token user's fork.nofalse
target-branchBranch targeted by the release pull request. Defaults to the repository default branch.no
config-fileOptional Release Please JSON config path. Exactly one package is supported.no
manifest-fileRelease Please manifest containing the last released version for the configured package.no.release-please-manifest.json
release-typeRelease strategy. This build supports simple only.nosimple
pathRelease a single package from this repository-relative directory. Defaults to the repository root.no.
initial-versionVersion used for the first release when the manifest has no configured package entry.no1.0.0
release-asForce the next release to a full SemVer version.no
tag-prefixExplicit tag prefix. Set to an empty string for tags such as 1.2.3.no
include-v-in-tagPrefix tags with v when tag-prefix is not supplied.notrue
include-v-in-release-namePrefix the Gitea Release display name with v.notrue
changelog-pathCumulative changelog path.noCHANGELOG.md
changelog-hostHost used for changelog commit and compare links.no
release-notes-pathDeprecated and ignored. Release notes come from CHANGELOG.md or the release PR body.no
extra-filesJSON array of additional generic, JSON, TOML, YAML, or XML version files.no
exclude-pathsJSON array of repository paths whose commits are excluded when all changed files match.no
commit-search-depthMaximum number of recent target-branch commits scanned while locating the previous release.no500
release-search-depthMaximum number of recent tags scanned when bootstrapping without an expected release tag.no400
bootstrap-shaExclusive commit boundary used before the first matching tag.no
last-release-shaExplicit exclusive commit boundary for release calculation.no
versioning-strategydefault, always-bump-patch, always-bump-minor, always-bump-major, or prerelease.nodefault
bump-minor-pre-majorUse a minor bump for breaking changes before 1.0.0.nofalse
bump-patch-for-minor-pre-majorUse a patch bump for features before 1.0.0.nofalse
prereleaseCreate prerelease versions and mark the Gitea Release as a prerelease.nofalse
prerelease-typePrerelease identifier such as beta.no
draftCreate the Gitea Release as a draft.nofalse
draft-pull-requestPrefix the release PR title with WIP because Gitea has no create-draft field.nofalse
skip-gitea-releaseSkip automatic tag and Gitea Release creation.nofalse
skip-github-releaseGoogle-compatible alias for skip-gitea-release.nofalse
skip-gitea-pull-requestSkip release pull request creation and updates.nofalse
skip-github-pull-requestGoogle-compatible alias for skip-gitea-pull-request.nofalse
skip-labelingDo not create or update lifecycle labels.nofalse
skip-changelogDo not update the changelog file.nofalse
labelComma-separated pending release PR labels.noautorelease: pending
release-labelComma-separated labels applied after publishing.noautorelease: tagged
extra-labelAdditional comma-separated labels for release PRs.no
pull-request-title-patternRelease PR title pattern using ${scope}, ${component}, ${version}, and ${branch?}.nochore${scope}: release${component} ${version}
pull-request-headerText placed before release notes in the pull request body.no:robot: I have created a release *beep* *boop*
pull-request-footerText placed after release notes in the pull request body.noThis PR was generated with [Gitea Release Please](https://github.com/kuddy-on/gitea-release-please-action).
signoffSignoff identity in Name <email@example.com> form for release commits.no
changelog-sectionsJSON array defining Conventional Commit types, section names, and hidden flags.no
include-commit-authorsInclude commit authors in generated changelog entries.nofalse
date-formatUTC release date format supporting %Y, %m, %d, and %F.no%Y-%m-%d
always-updateReport an unchanged managed release PR as updated.nofalse
namedescription
release_createdWhether this run created a Gitea Release.
releases_createdWhether this run created any Gitea Releases.
paths_releasedJSON array of released paths; either ["."] or [].
prs_createdWhether a release pull request was created or updated.
prCreated or updated release pull request object.
prsJSON array containing the created or updated release pull request.
upload_urlGitea release asset upload URL.
html_urlGitea Release web URL.
tag_namePublished tag name.
versionPublished SemVer version.
majorPublished major version.
minorPublished minor version.
patchPublished patch version.
shaTagged release PR merge commit.
bodyGitea Release body.
idGitea Release numeric ID.
nameGitea Release display name.
pathReleased package path; non-root releases expose the equivalent as <path>--path.
prNumberMerged release pull request number.
draftWhether the Gitea Release is a draft.
pr_createdCompatibility output indicating a release PR was created.
pr_updatedCompatibility output indicating a release PR was updated.
pr_numberCompatibility output containing the release PR number.